Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

set_keepout

Replace runtime keep-out boxes (max 16) for a reBot arm so motions entering them fail with WORKSPACE_VIOLATION; pass [] to remove all. Persisted on device.

Instructions

CONFIGURATION CHANGE: replace the runtime keep-out boxes (max 16; min_m < max_m per axis, metres, base frame). Motions into a box fail with WORKSPACE_VIOLATION. Pass [] to remove all. Persisted on the device. Show the user the boxes before setting them. Needs capability 'keepout'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "boxes": "<boxes>"
    },
    "name": "set_keepout"
  }
}

Input Schema

NameRequiredDescriptionDefault
boxesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/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: it discloses the 16-box cap, the min_m < max_m invariant, the failure mode (WORKSPACE_VIOLATION for motions into a box), persistence on the device, and a privilege requirement ('keepout' capability). It also flags that replacement overwrites existing boxes, which is the destructive aspect an agent must know.

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?

Front-loaded with 'CONFIGURATION CHANGE:' to signal a mutation, then constraints, failure mode, sentinel, persistence, user-confirmation guidance, and capability requirement — every clause carries information and none repeat the schema.

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 one-parameter mutation with no output schema and no annotations, this covers constraints, side effects, error behavior, persistence, and authorization. It does not describe what the call returns or how in-progress motions are handled at the moment of replacement, minor omissions.

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 description coverage is 0%, so the description must explain the single parameter — and it adds real meaning: max 16 entries, min_m < max_m per axis, units in metres, and coordinates in the base frame, plus the empty-list sentinel. It leaves the per-box 'name' field's purpose unstated, a minor remaining gap.

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 and resource ('replace the runtime keep-out boxes') with scope qualifiers (runtime, max 16), which naturally separates it from the read-side sibling get_keepout. An agent can tell exactly what this tool does without consulting the 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?

Gives concrete use conditions: pass [] to remove all, show the user the boxes first, and requires the 'keepout' capability. It does not name an alternative (e.g., set_collision_guard) or state when not to use this tool, so it falls short of fully explicit routing.

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