Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

release_control

Release the control lease on a reBot arm so the web cockpit can automatically reacquire it, freeing the held session for other control sources.

Instructions

Release the control lease (the web cockpit will acquire it automatically).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 does disclose a real side effect — the web cockpit acquires the lease automatically after release — which is valuable context an agent could not infer from the zero-parameter schema. However, it says nothing about what happens if the caller does not hold the lease, whether the call is idempotent, or whether it can fail.

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?

One sentence with the core action front-loaded, followed by a parenthetical that adds the single most important behavioral detail. No filler, nothing that could be cut without losing information.

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 zero-parameter lease-release tool with no annotations and no output schema, the description covers the action and its main consequence. The remaining gap — error behavior when no lease is held — is minor given the tool's simplicity.

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 nothing for the description to disambiguate. Baseline 4 applies; the description correctly avoids inventing arguments.

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?

Specific verb plus resource: 'Release the control lease.' An agent can immediately tell this is the inverse of take_control without opening the schema. It stops short of naming take_control explicitly, so it is not a full 5.

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?

Usage is only implied: you call this when you currently hold the lease and want to give it up. There is no explicit statement of preconditions (must the caller actually own the lease?), no when-not guidance, and no reference to take_control as the counterpart action.

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