Skip to main content
Glama

Route an envelope to an executor

soma_route

Pick an executor by capability, mandate and price. If no candidate fits, the refusal names every reason.

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": {
      "id": "<id>"
    },
    "name": "soma_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds genuinely useful failure semantics — a refusal enumerates every non-matching reason — but says nothing about what the successful call does to the envelope (reserve, dispatch, or merely record a selection) or how retries behave given the non-idempotent hint.

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 with no filler; the selection criteria come first and the failure-mode note second. Nothing is redundant or restated from the title.

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?

An output schema exists, so return values need not be explained, and the refusal behavior is covered. However, for a mutating, non-idempotent, open-world operation the description leaves out what 'id' refers to and what state change occurs on success, which an agent needs to call it safely.

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% for the single required 'id' parameter, so the description must compensate and it does not — it never mentions the identifier at all. An agent must infer from the title that this is an envelope id, and gets no format or scoping hints.

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 states a specific action ('Pick an executor') and names the selection criteria (capability, mandate, price), which tells an agent this is a routing/dispatch-decision tool rather than a registry lookup. It is clear on its own, but it never explicitly says 'envelope' or contrasts itself with siblings like soma_claim or soma_send, so differentiation comes mostly from the title.

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 statement of when to call this versus alternatives such as soma_claim or soma_send, and no prerequisites (e.g., whether the envelope must already exist or be registered). The only conditional given is about the no-match outcome, which is behavior rather than usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources