Skip to main content
Glama

reroute

Recompute alternatives for an active journey (requires auth).

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": {
      "journey_id": "<journey_id>",
      "current_position": "<current_position>"
    },
    "name": "reroute"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoconditions_changed
api_keyNo
journey_idYes
current_positionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered structurally. The description adds two pieces of real value beyond that: the auth requirement and the precondition that the journey be active. It does not say whether recomputed alternatives replace existing ones or are appended, which matters for a non-idempotent mutation.

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 short sentence with the key resource and precondition front-loaded and no filler. It is efficient, though its terseness leaves substance to be desired elsewhere rather than wasting words.

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 mutating, open-world tool with four undocumented parameters and a nested object, the description omits the essentials: what current_position must contain and what a recompute returns or invalidates. The existing output schema excuses it from explaining return values, but the input side remains critically underspecified.

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% across four parameters, including a free-form nested object (current_position with additionalProperties). The description never explains the expected shape of current_position or the meaning of the reason field's default 'conditions_changed'; the only link is '(requires auth)' loosely pointing at the api_key parameter.

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 verb and resource: 'Recompute alternatives for an active journey'. An agent can tell this is a re-planning operation rather than route creation or optimization, but it never names a sibling (e.g., optimize_route) to sharpen the boundary, so it falls short of full differentiation.

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?

'for an active journey' implicitly scopes use to journeys that already exist, and '(requires auth)' flags a precondition. However, there is no explicit guidance on when to reroute versus optimize_route or create_journey, and no stated exclusions or failure conditions.

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.