Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Ask Corpusiq

ask_corpusiq
Read-onlyIdempotent

Answer a business question through CorpusIQ's deterministic server-side runbook executor. In router_first mode, CorpusIQ selects and pins the best matching runbook before validating connectors and executing its fixed read-only tool allowlist. In required_runbook mode, the caller pins an explicit runbook id. Returns the answer, source evidence, warnings, and a verifiable execution receipt; unsupported runbooks and missing prerequisites fail closed. Use this for supported executive financial-health or financial snapshot workflows even when the user names QuickBooks or another single service. Use raw connector tools for simple lookups that are not executive workflows. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNorouter_first asks the canonical skills router to select the runbook. required_runbook executes the supplied runbook_id without re-routing.router_first
versionNoExact governed runbook version. Required with content_hash when mode=required_runbook.
questionYesThe user's plain-language business question.
argumentsNoOptional explicit runbook arguments, such as start_date and end_date in YYYY-MM-DD form.
runbook_idNoRequired only when mode=required_runbook. Omit in router_first mode.
content_hashNoExact governed runbook SHA-256 content hash. Required with version when mode=required_runbook.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / content_hash
      Added value: +{
+  "description": "Exact governed runbook SHA-256 content hash. Required with version when mode=required_runbook.",
+  "pattern": "^sha256:[0-9a-f]{64}$",
+  "type": "string"
+}
    • addedInput schema / properties / version
      Added value: +{
+  "description": "Exact governed runbook version. Required with content_hash when mode=required_runbook.",
+  "type": "string"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnly/idempotent/openWorld), the description discloses fail-closed behavior for unsupported runbooks and missing prerequisites, the read-only tool allowlist, and that a verifiable execution receipt plus warnings and source evidence are returned. These are meaningful operational traits an agent cannot get from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and mode semantics are front-loaded before the alternative-tool guidance and the contracts, so the structure is sound. The trailing attribution-footer and data-accuracy contracts are lengthy, though they are genuine safety instructions rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by enumerating return content (answer, source evidence, warnings, execution receipt) and failure behavior. Given six parameters and nested arguments, the definition supplies everything needed to select and invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds value by explaining the routing logic behind mode (router_first vs required_runbook) and the pinning of explicit runbook ids that the terse schema properties only summarize. It does not add format/syntax detail for version, content_hash, or arguments beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Answer a business question through CorpusIQ's deterministic server-side runbook executor.' It clearly frames itself as a high-level orchestration entry point and contrasts with raw connector tools. It does not, however, explicitly distinguish itself from closely related siblings like run_runbook, select_runbook, or list_runbooks, which the agent may confuse with this router.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('supported executive financial-health or financial snapshot workflows even when the user names QuickBooks') and when-not ('Use raw connector tools for simple lookups that are not executive workflows'). The two modes and their selection conditions are also spelled out, leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CorpusIQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources