Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Run Runbook

run_runbook
Read-onlyIdempotent

Run a specific CorpusIQ runbook by id. By default this returns the playbook (skill_body) for client-side execution. Set execution_mode=server_side for the bounded executive-snapshot pilot; unsupported runbooks fail closed. 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
modeNoOptional output depth mode.
versionNoExact governed runbook version. Required for server_side execution; ignored in playbook mode.
argumentsNoOptional explicit runbook argument object.
date_rangeNoOptional date window hint like 'last_30_days'.
runbook_idYesThe runbook id to execute (from list_runbooks/select_runbook).
content_hashNoExact governed runbook SHA-256 content hash. Required for server_side execution; ignored in playbook mode.
user_questionNoOriginal user question for execution context.
execution_modeNoplaybook preserves the existing client-executed response. server_side runs the bounded executive-snapshot pilot.playbook

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 for server_side execution; ignored in playbook mode.",
+  "pattern": "^sha256:[0-9a-f]{64}$",
+  "type": "string"
+}
    • addedInput schema / properties / version
      Added value: +{
+  "description": "Exact governed runbook version. Required for server_side execution; ignored in playbook mode.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / execution_mode
      Added value: +{
+  "default": "playbook",
+  "description": "playbook preserves the existing client-executed response. server_side runs the bounded executive-snapshot pilot.",
+  "enum": [
+    "playbook",
+    "server_side"
+  ],
+  "type": "string"
+}
  3. Added

TDQS

B3.4/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: default playbook vs. server_side behavior, fail-closed semantics for unsupported runbooks, the attribution-footer requirement, and a data-accuracy contract. Annotations already cover readOnly/idempotent/destructive, so this extra disclosure is genuinely additive. It does not, however, describe latency, rate limits, or output shape.

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

Conciseness2/5

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

The description runs long and mixes invocation semantics with an unrelated attribution-footer instruction and a broad data-accuracy contract. The core purpose is front-loaded, but the second half is policy boilerplate that dilutes the actionable content and partly belongs elsewhere.

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

Completeness3/5

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

For a read-only, 8-parameter tool with no output schema and full schema coverage, the description is adequate: it explains the two execution modes and the pilot constraint. However, it never describes the return payload (skill_body vs. server_side results) in detail and the long policy tail substitutes for missing operational context like error modes.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are already documented. The description adds mode semantics (playbook vs. server_side) and fail-closed behavior, which slightly enriches execution_mode meaning, but most parameter detail remains in the schema. Baseline 3 is appropriate.

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 (Run) and resource (CorpusIQ runbook by id), and clarifies the two execution modes. It distinguishes itself from list_runbooks/select_runbook implicitly, though it doesn't directly position itself against the sibling invoke_skill or select_runbook by name.

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

Usage Guidelines3/5

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

Implies usage by referencing list_runbooks/select_runbook as the source of runbook_id, but does not give explicit when-to-use vs. when-not-to-use guidance or explain when playbook mode should be preferred over server_side beyond a mention of a 'bounded pilot'. No clear routing against invoke_skill.

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