Skip to main content
Glama

clear_emergency_stop

Destructive

Release a robot's emergency stop so it can move again. Clears the stop state by robot ID, restoring motion after a halt.

Instructions

Release an emergency stop so the robot can move again.

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": "clear_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.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the agent knows this is an unsafe, non-repeatable mutation. The description adds the practical consequence (the robot regains motion), but for a safety-critical action it omits any warning about prerequisites, authorization, or failure behavior — a meaningful gap that the annotations alone do not fill.

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?

One short sentence, front-loaded with the action and followed immediately by its effect. No redundant wording, no restating of the title, nothing to trim.

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

Completeness3/5

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

For a single-parameter tool with no output schema the mechanical coverage is fine, but this is a destructive, safety-critical operation and the description says nothing about the state required to succeed, permission needs, or what happens if the stop cannot be released. That leaves a real gap for an agent deciding whether it is safe to invoke.

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 (robot_id) with 100% schema description coverage including an example, so the schema carries the full burden. The description adds no additional meaning about the identifier or its format, which is acceptable but is the baseline rather than added value.

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 pairs a specific verb ("Release") with a specific resource ("an emergency stop") and states the resulting effect ("so the robot can move again"). It is clearly the inverse of the sibling emergency_stop, though it never names that sibling or any other alternative explicitly.

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?

Usage is only implied: an agent can infer this applies after an e-stop has been engaged, but there is no explicit statement of when to call it, what preconditions must hold (e.g. hazard cleared, physical reset performed), or when not to call it.

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