Skip to main content
Glama

plan_route

Read-onlyIdempotent

Calculate a robot's route distance, duration, required battery, and whether it can reach the goal above reserve without moving the robot.

Instructions

Plan a trip without moving: distance, duration, battery needed and whether the robot would arrive above the battery reserve.

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": {
      "robot_id": "<robot_id>",
      "goal": "<goal>"
    },
    "name": "plan_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesLocation name from list_locations
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and the description is consistent with them by stating "without moving." It goes beyond the annotations by disclosing what the computation actually yields: distance, duration, required battery, and a reserve-threshold check — genuinely useful behavioral detail.

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?

A single sentence with zero filler, front-loaded with the action and immediately followed by the outputs. Nothing could be cut without losing information.

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

Completeness4/5

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

With only two required params and no output schema, the description does the important remaining work of enumerating the return values, including the battery-reserve verdict. An agent has enough to decide to call it and to interpret the result.

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

Parameters3/5

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

Schema coverage is 100%: both robot_id and goal are documented, including that goal comes from list_locations. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

"Plan a trip" is a specific verb plus resource, and the phrase "without moving" implicitly separates it from the execution sibling navigate_to. It doesn't name that sibling, so an agent must infer the pairing, but the purpose is unmistakable.

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?

"Without moving" strongly implies a dry-run/simulation use case, which is useful guidance. However, it never explicitly says to call this before navigate_to, nor when not to use it, so the routing decision is left to inference.

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