Skip to main content
Glama

navigate_to

Destructive

Drive a warehouse robot to a named goal location using its robot ID and a location from list_locations.

Instructions

Drive a robot to a named location.

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": "navigate_to"
  }
}

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

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and non-idempotent, but the description offers no explanation of why: whether an in-progress task is cancelled, whether the robot must be idle, or what happens if navigation fails. For a destructive motion command, that extra context is exactly what the description should supply and does not.

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?

A single short sentence with no filler, front-loaded on the action and target. It is efficient, though its brevity borders on under-specification for a destructive motion command.

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?

The tool is a destructive, non-idempotent robot motion command with no output schema documenting return values. The definition says nothing about preconditions, side effects, failure behavior, or what a caller gets back, which leaves significant gaps for its complexity.

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%, so both robot_id and goal are already documented, including the pointer to list_locations for valid names. The description adds nothing 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?

The description gives a concrete verb and resource: 'Drive a robot to a named location.' An agent can immediately tell it initiates motion toward a named goal. It does not, however, distinguish itself from siblings like plan_route or dock, which also concern robot movement.

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 when-to-use or when-not-to-use guidance. The presence of siblings such as plan_route and dock makes the missing routing decision important, and the description leaves the agent to infer that this both plans and executes.

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