Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

take_control

Acquire the control lease for a reBot arm when no other client holds it, enabling AI agents to command motion and gripper actions; cannot override the web cockpit.

Instructions

Acquire the control lease when no other client holds it. Cannot take control from the web cockpit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the exclusivity precondition and the web cockpit limitation, but omits failure behavior, whether the call blocks, lease duration, and what control actually enables.

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?

Two short sentences, front-loaded with the primary action and followed by the key constraint. There is no wasted wording.

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

Completeness3/5

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

For a zero-parameter tool this is close to sufficient, but with no annotations and no output schema the description should say more about what happens when acquisition fails and how the lease is later released. The core condition and cockpit exclusion are covered, but the behavioral picture remains thin.

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 has zero parameters, so the baseline is 4 and the description does not need to explain parameter meaning. The schema is essentially empty and the description does not contradict it.

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 names a specific action and resource: acquiring the control lease. It also states the key eligibility condition, no other client holds it, so the tool is distinguishable from release_control. It stops short of explicitly naming the counterpart tool or fully explaining the control model.

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?

It gives a clear when-to-use condition (when no other client holds the lease) and an explicit exclusion (cannot take control from the web cockpit). It does not say what to do if the lease is unavailable or name the natural alternative release_control.

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