Skip to main content
Glama

routeseal_check

Retrieve the verdict class and named clause for a sealed dispatch-point routing decision using its seal ID. Verify routing compliance from captured facts and policy versions.

Instructions

Counterparty view: the verdict class and the named clause only. 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_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
dispatch_seal_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses 'Unmetered' and a restricted output scope, but does not state read-only behavior, idempotency, authorization requirements, error handling, or what happens with an invalid seal ID.

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?

The description is very short and front-loads the limited-view concept with no filler. It is concise, though the terseness contributes to ambiguity around the tool's exact operation.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and 0% parameter schema coverage, the description is under-specified. It names the returned fields but does not explain the sole required parameter, output meanings, or access behavior sufficiently for reliable invocation.

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

Parameters2/5

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

Schema description coverage is 0%, and the description never mentions dispatch_seal_id. The parameter name is self-descriptive as an identifier, but the description adds no format, source, or meaning beyond the raw schema.

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

Purpose3/5

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

The description indicates a restricted view returning 'the verdict class and the named clause only,' which gives some sense of the resource and output scope. However, it lacks an explicit verb such as 'retrieve' or 'check' and uses domain jargon like 'Counterparty view' without clarifying what is being checked.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or comparison to sibling tools such as routeseal_get_verdict. 'Counterparty view' implies a limited external-facing use case, but the description does not state when this tool should be chosen over alternatives.

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