Skip to main content
Glama

routeseal_export_captures

Exports a sealed capture with its receipt chain head plus grammar and policy versions, enabling independent recomputation of routing verdicts.

Instructions

Export a sealed capture with the receipt chain head and the grammar and policy versions, for independent recomputation. Unmetered.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dispatch_seal_id": "<dispatch_seal_id>"
    },
    "name": "routeseal_export_captures"
  }
}

Input Schema

NameRequiredDescriptionDefault
dispatch_seal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It adds one genuinely useful trait ('Unmetered', i.e. no quota cost) and indicates the export is self-contained, but it does not state whether the call is read-only or has side effects, what permissions are needed to export a sealed capture, or whether exports are idempotent. The plural tool name 'captures' also conflicts mildly with the singular 'a sealed capture'.

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?

One well-formed sentence front-loads the action and payload, followed by a terse 'Unmetered.' fragment that earns its place as a behavioral note. Nothing is wasted, though the trailing fragment and plural-name mismatch slightly reduce polish.

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 single-parameter tool with no output schema and no annotations, the description covers the payload's conceptual contents but omits the return format, how to obtain the required seal id, and any permission model. Adequate to attempt a call, but not enough to invoke it confidently without trial and error.

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 0% for the single parameter dispatch_seal_id, so the schema supplies no meaning. The description implies the parameter identifies 'a sealed capture' but never explains the id's format, where it comes from (presumably routeseal_seal_dispatch), or whether it is the seal id versus a capture id — leaving the most important input under-explained.

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?

The description names a specific verb ('Export') and resource ('a sealed capture') and enumerates what the export contains: the receipt chain head plus the grammar and policy versions. The stated goal ('for independent recomputation') hints that this differs from the routeseal_recompute sibling, though no sibling is named explicitly.

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?

The phrase 'for independent recomputation' implies the use case — offloading verification to an external party — but the definition gives no explicit when-to-use versus when-not guidance, and does not say how this differs from calling recompute directly or when to prefer one over the other.

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