Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

get_keepout

Retrieve the keep-out box definitions that specify zones the reBot arm must not enter, returning each box name and min/max bounds so agents can plan collision-free motion.

Instructions

Keep-out boxes the arm must not enter: {boxes[{name, min_m, max_m}], source}. No lease needed. Needs capability 'keepout'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 disclose real behavioral facts: no lease acquisition is required before calling, and the 'keepout' capability must be present. It also reveals the return structure rather than leaving the caller to guess, though it never states side effects (none expected for a getter) or what 'source' in the payload means.

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 short clauses, front-loaded with the resource and its return shape, followed by the two preconditions. Every clause earns its place and nothing is padded.

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?

Because no output schema exists, the description must supply the return shape — and it does, including field names and metric units from the '_m' suffixes. The only loose end is the unexplained 'source' field, a minor gap for a zero-argument getter.

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 add and the baseline of 4 applies. Nothing in the description misleads about inputs.

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?

States the resource precisely as 'keep-out boxes the arm must not enter' and even gives the return shape {boxes[{name, min_m, max_m}], source}. The verb is only implied by the name 'get_keepout', and no sibling is named, but an agent can still tell this is the read counterpart to set_keepout rather than a mutation.

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?

No explicit when-to-use statement or named alternative appears. The two trailing clauses — 'No lease needed' and "Needs capability 'keepout'" — do function as invocation preconditions, telling the agent this can be called without take_control and only when the keepout capability exists, which is implied guidance but not a full routing rule.

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