Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

e_stop

Triggers an emergency stop for a reBot arm without requiring a lease, latching the stop state until a person clears it in the web cockpit.

Instructions

Emergency stop. Needs no lease; latches EStop until a person clears it in the web cockpit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "e_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description carries the full burden and does meaningful work: it discloses that no lease is required, that the stop latches (i.e., persists rather than auto-releasing), and that only a human in the web cockpit can clear it. That last point is the critical operational fact an agent needs. It does not describe the immediate physical effect on motion or whether any in-flight command is aborted.

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, front-loaded with the action and followed by the two facts that govern invocation and aftermath. No filler, no restatement of the tool name.

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 zero-parameter, no-output-schema safety tool, the definition covers the essentials: callable without a lease, latching semantics, and human-only recovery. The remaining gap is the physical consequence of the call, which would help an agent decide whether to invoke it before or after other safety actions.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the schema is fully self-describing. Baseline 4 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 opens with a specific verb+resource ("Emergency stop") and immediately characterizes the effect as a latched EStop, which separates it from the plain sibling `stop`. It stops short of naming that sibling explicitly, so the differentiation is implied rather than stated.

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?

"Needs no lease" tells the agent this is callable even when it does not hold control, which is real usage context, and the word "Emergency" implies the trigger condition. However, it never says when to prefer this over `stop` or `recover`, nor that it should be reserved for genuine emergencies.

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