Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

describe_safety

Read the arm's safety capabilities before planning motions: stops, faults with recoverable flags, speed and joint limits, timing, and whether a physical e-stop exists.

Instructions

What the arm's safety system does and does not do: stops, faults (with recoverable flags), speed and joint limits, timing, and hardware facts such as whether a physical e-stop exists. Plus a one-line 'summary'. Read it before planning motions. No lease needed. Needs capability 'safety_describe'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the important operational facts: no lease is required (so it is safe to call without control) and the caller needs the 'safety_describe' capability. It also compensates for the missing output schema by listing what comes back, including recoverable fault flags and a one-line summary; it stops short of stating explicitly that the call has no side effects on robot state.

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?

The main payload (what the report contains) is front-loaded, followed by short imperative sentences for prerequisites. The telegraphic parenthetical '(with recoverable flags)' and 'Plus a one-line summary' are slightly compressed but each carries real information, so nothing is wasted.

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-argument, read-only introspection tool with no output schema, the description covers purpose, prerequisites, timing of use, and the shape of the returned report. Only the precise structure/format of the fault flags and limits is left unspecified, which is a minor gap given there is no output schema to defer to.

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; baseline applies. The description's only argument-like content is the capability prerequisite, which is a useful non-schema constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (describes the arm's safety system) and enumerates its contents: stops, faults with recoverable flags, speed and joint limits, timing, hardware e-stop facts. That enumeration distinguishes it from siblings like get_state or collision_guard_status without the agent needing to open any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger: 'Read it before planning motions', which tells the agent where this fits in a workflow. It does not name alternatives or state when not to use it (e.g., versus get_state or collision_guard_status), so it falls short of a 5.

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