Skip to main content
Glama

routeseal_recompute

Recomputes a routing verdict from an exported capture plus grammar and policy versions without service state, enabling offline verification of dispatch decisions.

Instructions

Recompute a verdict from an exported capture plus the grammar and policy versions, with no service state. 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_capture": "<dispatch_capture>",
      "grammar_version": "<grammar_version>",
      "policy_version": "<policy_version>"
    },
    "name": "routeseal_recompute"
  }
}

Input Schema

NameRequiredDescriptionDefault
policy_versionYes
grammar_versionYes
dispatch_captureYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful traits — no service state (pure/deterministic computation, no side effects on the service) and unmetered (no quota cost) — but says nothing about what happens if versions don't match the capture, whether the recomputed verdict can diverge from a stored one, or error behavior.

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

Conciseness5/5

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

Two short sentences, no filler, and the core operation is front-loaded ahead of the qualifiers. Every clause adds information.

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

Completeness4/5

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

Given three required params, one nested object, no output schema and no annotations, the description covers the essential concept and two key behavioral traits. The remaining gaps — return shape and provenance of the version strings — are real but modest for a pure recomputation tool.

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 coverage is 0%, so the description must compensate, and it partially does: it names all three inputs conceptually (exported capture, grammar version, policy version). It adds no detail on where the version strings come from, what format they take, or what fields the nested dispatch_capture object must contain.

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 (recompute) and resource (a verdict) plus the three ingredients it consumes, which is far more than a restatement of the name. It does not explicitly contrast itself with routeseal_check or routeseal_get_verdict, so an agent must infer that this is the offline/deterministic path.

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?

'With no service state' and 'Unmetered' implicitly signal the use case: reproducing a verdict without touching the live service and without consuming quota. However, no explicit when-to-use or when-not-to-use statement names the alternatives (check, get_verdict), so the agent has to reason about the choice.

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