Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

move_to_pose

Moves the reBot arm in joint space to a saved pose at a configurable speed scale, blocking until motion completes. Use it to return to or execute stored arm positions.

Instructions

Joint-space move to a saved pose; speed_scale 0.1..1.0 of the planned speed. Blocks until done.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "move_to_pose"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
speed_scaleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 that the call blocks until completion and that speed_scale scales the planned speed, but it omits prerequisites like control ownership, collision/safety state, failure behavior, and whether stop can interrupt the motion.

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 description is two compact sentences with the main action front-loaded. Every clause adds useful information: joint-space motion, saved-pose target, speed scaling, and blocking behavior.

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 robot motion tool with no annotations, no output schema, and 0% schema description coverage, the description covers the core action, speed semantics, and blocking behavior. It remains incomplete regarding safety prerequisites, control state, and failure handling, which an agent would need before invoking it in a real robot context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains speed_scale as a fraction of planned speed and gives its range, and 'saved pose' implies what name means, but it does not clarify name lookup, invalid-name behavior, or the default speed_scale effect.

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 and resource: a joint-space move to a saved pose. It partially distinguishes itself from siblings via 'saved pose' and 'joint-space,' but does not explicitly contrast itself with move_to or move_relative.

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: use this when moving to a named, previously saved pose. However, the description gives no explicit when-to-use guidance versus alternatives such as move_to or move_relative, and no preconditions or exclusions are stated.

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