Skip to main content
Glama

emergency_stop

Idempotent

Immediately halt a specified robot and keep it stationary until the stop is cleared.

Instructions

Stop a robot immediately. It will not move until the stop is cleared.

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>"
    },
    "name": "emergency_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so safety framing is partly covered. The description adds genuinely new behavioral context: the stop is latching and the robot remains immobile until explicitly cleared, which is the key operational trait an agent needs and is not derivable from the annotations.

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 zero filler, and the critical fact (immediate stop) is front-loaded before the latching consequence. Nothing could be removed 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?

For a one-parameter mutation tool with full annotation coverage and no output schema, the description covers purpose, urgency, and latching behavior adequately. The only missing piece is how the stop is released (naming clear_emergency_stop), which would complete the operational loop.

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?

There is a single parameter with 100% schema description coverage (robot_id with an example format), so the schema already carries the semantics. The description adds no further meaning about identifier format, scoping, or behavior when an unknown robot_id is supplied, which is the baseline expectation when schema coverage is complete.

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 uses a specific verb and resource ('Stop a robot') and qualifies the mode ('immediately'), so the action is unmistakable. It also implicitly distinguishes itself from the clearing counterpart by noting the stop persists 'until the stop is cleared', though it never names that sibling tool.

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?

The word 'immediately' signals this is the urgent/halt path, and 'until the stop is cleared' hints that a separate clearing step exists. However, it never explicitly states when to prefer this over alternatives like navigate_to interruption, nor does it name clear_emergency_stop as the follow-up, leaving the agent to infer the recovery path.

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