Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

recover

Clears armd faults marked clearable, including watchdog timeout, control deadline, and unsettled handover, then restores torque; other faults and E-stops stay latched for manual clearing.

Instructions

Clear a fault that armd marks recoverable (WATCHDOG_TIMEOUT, CONTROL_DEADLINE, HANDOVER_UNSETTLED) and turn torque on again. Any other fault or an E-stop returns NOT_RECOVERABLE and stays latched for a person to clear in the web cockpit. Needs capability 'fault_codes'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does well: it discloses the physical side effect of re-enabling torque, the failure mode and its return value (NOT_RECOVERABLE), that faults stay latched, and the required capability 'fault_codes'. It stops short of stating what a successful call returns or whether motion becomes immediately possible.

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?

Three tight sentences, front-loaded with the action and its allowed fault set, followed by the exclusion and the permission requirement — no filler or repetition.

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 but safety-critical operation with no annotations and no output schema, the definition covers side effects, failure semantics and authorization. The only gap is the success-path return/next-state, which an agent might want before invoking.

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 input schema has zero parameters, so there is nothing for the description to clarify; baseline applies.

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?

States a specific verb + resource ('Clear a fault') and then enumerates exactly which fault classes are recoverable (WATCHDOG_TIMEOUT, CONTROL_DEADLINE, HANDOVER_UNSETTLED), which lets an agent tell this apart from e_stop/enable without opening a schema.

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

Usage Guidelines5/5

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

Explicitly gives both the when (recoverable faults only) and the when-not (any other fault or an E-stop returns NOT_RECOVERABLE and must be cleared by a person in the web cockpit), including the fallback path when this tool is not applicable.

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