Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

set_collision_guard

Enable or disable the robotic arm's collision guard and set its sensitivity to low, medium, or high; contact stops the arm, and repeated trips latch a collision fault.

Instructions

CONFIGURATION CHANGE: switch the collision guard on or off and/or set its sensitivity (low, medium, high). Persisted on the device. With the guard on, contact stops the arm; it resumes by itself when the contact is gone and latches a COLLISION fault after repeated trips. Thresholds are uncalibrated placeholders. Use only when the user asks. Needs capability 'collision_guard'.

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

Input Schema

NameRequiredDescriptionDefault
enabledNo
sensitivityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/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 so well: it discloses that changes are 'Persisted on the device', describes the runtime effect (contact stops the arm, auto-resume on release, a latched COLLISION fault after repeated trips), warns thresholds are 'uncalibrated placeholders', and states the required 'collision_guard' capability.

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?

Four dense sentences, each front-loading value: action first, then persistence, then behavioral consequences, then usage restriction and prerequisite. Nothing is redundant or padded.

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

Completeness5/5

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

For a two-optional-parameter configuration tool with no output schema and no annotations, the description covers action, side effects, caveats, and capability requirements — everything an agent needs to call it correctly and warn the user about uncalibrated thresholds.

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?

Schema coverage is 0%, so the description must carry parameter meaning. It documents both parameters — enabled as on/off and sensitivity with its exact enum values — and the 'and/or' phrasing conveys that either can be set independently, which matters given both are optional and nullable. It does not explicitly say what happens when a parameter is omitted/null.

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 opens with a specific verb+resource ('switch the collision guard on or off and/or set its sensitivity') and names the exact value space (low, medium, high). An agent can immediately distinguish this configuration tool from the read-only 'collision_guard_status' sibling.

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?

'Use only when the user asks' is a genuine when-not-to-use constraint (do not act proactively), which is real guidance. However, no alternative is named for reading current state (e.g., collision_guard_status), and nothing indicates what to do if the capability is missing beyond stating it is required.

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