Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

park

Moves the reBot arm to its resting pose and turns torque off to end Idle, blocking until the motion completes.

Instructions

Park at the resting pose and turn torque off (ends Idle). Blocks until done.

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

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 supplied, the description carries the full disclosure burden. It usefully reveals that torque is disabled, Idle is exited, and the call blocks until completion. It does not disclose whether the robotic arm may drop or require support once torque is off, whether control ownership or an enabled state is required, or what errors occur if parking is interrupted.

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?

The definition is a single compact sentence with the physical action front-loaded and the state effect plus blocking behavior appended. Every clause conveys distinct information, with no filler or redundancy.

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 tool with no output schema, the description covers the essential action, state transition, and blocking behavior. The remaining gap is safety context around disabling torque; with no annotations, that omission is noticeable but the core operational picture is present.

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 are no parameter semantics for the description to explain. The baseline for a no-parameter schema applies, and the description appropriately omits parameter detail rather than inventing any.

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 states a specific action pair: move to a resting pose and disable torque, plus the state transition (ends Idle). This is clearly more than a restatement of the name 'park'. It does not explicitly contrast with the sibling 'home', which is the most likely source of confusion for an agent choosing a resting operation.

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 implied rather than stated: the '(ends Idle)' note suggests it is invoked from the Idle state to finish a session, and 'turn torque off' signals a deactivation intent. There is no explicit when-not guidance and no named alternative such as stop, e_stop, home, or recover for cases where the robot should not relinquish torque.

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