Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

collision_guard_status

Retrieves collision guard configuration and current trip status for a reBot arm, showing whether protection is enabled, sensitivity and thresholds, plus active collision details.

Instructions

Collision guard configuration: {enabled, sensitivity, thresholds_nm}. get_state.collision shows a trip in progress (active, joint, residual_nm, resume_in_s). The guard is off by default and its thresholds are uncalibrated placeholders. No lease needed. 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": "collision_guard_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that the guard is off by default, that thresholds are uncalibrated placeholders (a critical caveat about trusting the values), that no lease is required, and that the 'collision_guard' capability is a prerequisite. It does not state failure behavior when the capability is absent, but the safety-relevant defaults are surfaced well beyond what structured fields provide.

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?

Four short sentences, front-loaded with the configuration shape and followed by the routing hint, the default-state caveat, and the capability requirement. The notation-heavy field lists ({enabled, sensitivity, thresholds_nm}) are dense but information-dense; nothing is padding, though the telegraphic style slightly reduces readability.

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?

There is no output schema, so the description must describe the return, and it does so by naming the configuration keys and cross-referencing get_state.collision for trip fields. Combined with the lease and capability notes, an agent has enough to call it correctly; only the behavior on a missing capability and the units/interpretation of sensitivity are left unstated.

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 no parameter semantics to explain and the baseline of 4 applies. The field list in the description actually documents the return shape rather than inputs, which is useful but not strictly this dimension's concern.

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 identifies the resource specifically and enumerates the configuration fields returned ({enabled, sensitivity, thresholds_nm}), so an agent knows what it inspects. It lacks an explicit verb (read/fetch) and only implicitly signals a read of current state, but it clearly differentiates itself from get_state.collision, which is named as the tool for an in-progress trip.

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?

Guidance is implied rather than stated: by pointing at get_state.collision for trip status, it suggests this tool is for the static configuration instead. There is no explicit 'use this when' or 'do not use for' phrasing, and no mention of the sibling set_collision_guard as the write-side alternative, leaving the agent to infer the pairing.

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