Horizon

Asks Horizon's Superconsultant a question about one company's organizational data. Streams the answer as MCP progress notifications, then returns the assembled answer and a `thread_id`. Stateful: the conversation is backed by a Superconsultant thread, and passing a `thread_id` continues it. `company_id` is required and comes from `list_companies`; `workspace_id` comes from `list_workspaces` and is required for workspace-only users, optional for company admins. The Horizon data the agent can read is limited to the (company, workspace) scope passed, which is enforced server-side on every call; it can also search the public web when a question calls for it. Answer quality depends heavily on how the question is scoped — `get_prompting_guide` documents how to scope one well. Beyond answering, the Superconsultant can act on the company's data when a question asks it to, including creating initiatives, so a call may write as well as read.

superconsultant_ask

Returns Horizon's guide to prompting `superconsultant_ask`: how to scope a question, the vocabulary that routes it to the right analysis, the output shapes it supports, and what each error code means. Answer quality depends heavily on how the question is phrased, and this guide is what documents that. Takes no arguments, reads no company data, and is unmetered.

get_prompting_guide

Lists the companies the authenticated user can scope a question to, returning each eligible company's id and name. These ids are the valid values for the `company_id` that `superconsultant_ask` requires.

list_companies

Lists the workspaces the authenticated user can access inside one company, returning each accessible workspace's id and name. These ids are the valid values for `superconsultant_ask`'s `workspace_id`, which workspace-only users must pass on every ask. Company admins may pass one to narrow an ask to a single workspace, or omit it for company-wide reach.

list_workspaces