Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

home

Move the robot arm to its predefined rest pose and block until the motion finishes.

Instructions

Move to the home pose. 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": "home"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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, and "Blocks until done" is a genuinely useful behavioral trait: the call is synchronous and returns only after motion completes. However, it does not say whether the call fails if the robot is not enabled/under control, whether it can be interrupted by stop/e_stop, or whether it reports arrival status.

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 with zero waste; the action is front-loaded and the blocking behavior follows immediately. Nothing is padded or repeated from the name.

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-param, no-output-schema motion command the description is close to sufficient, but as a physical robot action with no annotations it should at least indicate required preconditions (control/enable state) and failure behavior. Those gaps are the main reason it falls short of complete.

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 the schema is fully self-explanatory and the description needs only to confirm there is nothing to specify. Baseline 4 applies for a parameterless tool.

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 a specific verb ("Move") and a specific target ("the home pose"), so an agent can tell this is a canned motion to a predefined pose rather than a parameterized move like move_to or move_to_pose. It does not explicitly differentiate itself from the sibling park, which likely has overlapping intent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given; the agent must infer that this is the reset/rest position command. There is also no mention of prerequisites (e.g., whether control must be taken or the arm enabled first) or of what alternative to pick when a specific pose is needed instead of home.

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