ask_corpusiq: Deterministic Single-Tool Access to Business Data¶
ask_corpusiq is the high-level MCP tool that gives AI clients a single
entry point to the user's connected business data. Instead of exposing
dozens of connector tools and letting the model decide which to call, the
client sees one tool. CorpusIQ decides the rest: which skill to run, which
connectors to use, how to validate, and how to answer.
Why one tool¶
Every tool exposed to a client model is a decision point. Models are good at tool selection, but the selection is not deterministic. A user question about revenue could route to QuickBooks, Stripe, or a generic answer depending on the model's judgment. The one-tool design minimizes model discretion: the model makes a single decision (does this question need CorpusIQ?), and control transfers to the engine.
Modes¶
- Router-first: the engine resolves intent, selects the skill, and routes to the required connectors
- Required-runbook: a named runbook is bound by version, validated, and
executed fail-closed. If the runbook cannot complete, the tool returns
runbook_failedinstead of a normal answer
Execution guarantees¶
- Pinned allowlisted execution: only connectors and tools declared for the skill are reachable
- JWT enforcement: every call is authenticated and attributed
- Bounded failures: errors fail fast with a machine-readable receipt
- Evidence: every number in the answer carries a source reference
- Routing metadata: the answer records which skill, version, and connectors produced it
- Execution receipts: a machine-readable record of what ran, in what order, and the result of each step
Relationship to runbook.v1¶
ask_corpusiq is the production implementation of the runbook.v1 execution
contract. The specification and reference implementation are public at
github.com/CorpusIQ/runbook-spec,
and the governance proposal is under discussion in the MCP repository:
issue #3270.