Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

stop

Halt current motion and hold position with torque enabled, even while another tool runs.

Instructions

Stop the current motion and hold position (torque stays on). Works while another tool runs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that torque remains on and that it can be invoked while another tool is running, which is real post-condition and concurrency information. It omits whether the call blocks, whether the interrupted motion can be resumed, and whether an active motion is aborted or merely paused.

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 waste, and the core action and its resulting state are front-loaded before the concurrency note.

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, safety-relevant stop tool, the description covers the action, the post-state, and concurrent invocation. The remaining gap is resumption/blocking semantics, which is meaningful but not fatal given the tool's simplicity.

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 with 100% schema coverage, so there is nothing for the description to clarify. Baseline of 4 applies; the description does not need to discuss parameters at all.

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?

"Stop the current motion" states a specific verb and resource, and "hold position (torque stays on)" adds the resulting state. It does not explicitly name how it differs from the sibling e_stop, though the torque-stays-on detail implicitly marks this as a soft stop rather than an emergency halt.

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?

"Works while another tool runs" gives one concrete usage condition (concurrent invocation during an in-flight motion). However it never says when to prefer this over e_stop, nor what happens after the stop is issued, so the agent must infer the boundary between the two stop tools.

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