Skip to main content
Glama

routeseal_seal_dispatch

Seal a routing decision at dispatch with adapter attestation and mint a verifiable policy verdict, so anyone can recompute whether the chosen target followed policy.

Instructions

Seal a routing decision at a buyer-controlled dispatch point, through the dispatch-point adapter channel with the adapter's attestation, and mint the verdict under the operator's stated routing policy. One metered op per dispatch seal; decision-only and below-standard captures do not meter. Routeseal seals the routing decision at the moment of dispatch — the task, the candidates the router passed over, the target it chose, and the reason it stated. If the choice diverged from your stated routing policy, or picked an affiliated target over the policy's preferred candidate, the sealed record says so, and anyone can recompute the verdict from the record itself.

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": {
      "task_digest": "<task_digest>",
      "selected_target": "<selected_target>",
      "stated_reason": "<stated_reason>",
      "policy_version": "<policy_version>",
      "dispatch_point_id": "<dispatch_point_id>",
      "dispatch_timestamp": "<dispatch_timestamp>",
      "binding_ref": "<binding_ref>",
      "source": "<source>",
      "adapter_attestation": "<adapter_attestation>"
    },
    "name": "routeseal_seal_dispatch"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
binding_refYes
task_digestYes
candidate_setNo
stated_reasonYes
policy_versionYes
selected_targetYes
affiliation_flagsNo
dispatch_point_idYes
dispatch_timestampYes
adapter_attestationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose non-obvious behavior: a per-seal metered billing rule with carve-outs, the requirement that the seal flow through the adapter with its attestation, that the record flags policy divergence and affiliation preference, and that the verdict is independently recomputable. It omits auth/permission requirements, idempotency on repeat seals, and failure modes, which keeps it short of a 5 for a mutation tool.

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

Conciseness3/5

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

Content is front-loaded with the core action first, but the opening sentence is overloaded with jargon, and the third sentence ('Routeseal seals the routing decision at the moment of dispatch…') largely re-states the first before adding new detail. Trimming that restatement would tighten it without losing information.

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 an 11-parameter mutation tool with no annotations and no output schema, the definition explains the conceptual payload well but leaves gaps: it never says what the call returns (a seal record identifier or verdict object), how duplicate seals at the same dispatch point behave, or what authorization the adapter channel requires.

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 description coverage is 0% across 11 parameters including a nested candidate object, so the description must compensate — and it does for most: candidate_set ('the candidates the router passed over'), selected_target, stated_reason, policy_version, dispatch_point_id, adapter_attestation, and affiliation semantics all get conceptual meaning. Still undocumented are source, binding_ref, and dispatch_timestamp format expectations.

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 and resource — seal a routing decision at a buyer-controlled dispatch point via the dispatch-point adapter channel — and the third sentence enumerates exactly what gets captured (task, passed-over candidates, chosen target, stated reason). It never names a sibling (routeseal_check, routeseal_recompute) to contrast with, so differentiation is left to the agent.

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?

Usage is implied rather than stated: this is the act of sealing, as opposed to checking or recomputing elsewhere. The metering note ('one metered op per dispatch seal; decision-only and below-standard captures do not meter') gives some selection signal, but there is no explicit when-to-use, when-not-to-use, or alternative routing guidance.

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