Skip to main content
Glama

optimize_route

Read-only

Ranked routes with cost_breakdown and explanation (shortest is not always best).

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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "optimize_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYes
profileNosafest
waypointsNo
prioritiesNo
destinationYes
vehicle_classNocar
departure_timeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only a weak behavioral hint that ranking is not distance-only; it says nothing about how profile='safest', vehicle_class, or priorities change results, nor about external data sources implied by openWorldHint. With the bar lowered by annotations, this is a modest but insufficient contribution.

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?

It is a single sentence with no filler, so there is nothing to trim. The problem is the opposite of verbosity: the space saved is spent on the output shape rather than on scope, inputs, or alternatives, so brevity here costs information rather than adding clarity.

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?

An output schema exists, so explaining cost_breakdown and explanation is partly redundant, and the description cannot rely on annotations or schema text for the seven parameters. For an open-world routing tool with nested objects, null defaults, and a default profile, the definition leaves the agent without enough to call it correctly. It is technically non-empty but incomplete relative to the tool's complexity.

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

Parameters1/5

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

Schema description coverage is 0% across 7 parameters, and the description supplies no meaning for profile, priorities, vehicle_class, waypoints, or departure_time — including the nested origin/destination objects. The only field it mentions, cost_breakdown, is a return value, not an input. For a zero-coverage schema, the description must compensate, and it does not.

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 names the resource ('Ranked routes') and hints at a multi-criteria optimization output (cost_breakdown, explanation), which distinguishes it somewhat from pure lookups like get_route_conditions or reroute. However, it never states an action verb such as 'compute' or 'optimize a route between origin and destination', so the agent must infer the operation from the tool name. It reads more like a return-value summary than a purpose statement.

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 and no mention of alternatives, even though siblings like get_route_conditions, reroute, and create_journey plausibly overlap. The parenthetical 'shortest is not always best' implies a scenario (multi-objective routing) but stops short of telling the agent when to pick this tool over the others.

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.