Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

move_to

Move the robot's end link in a straight line to target X, Y, Z coordinates in the base frame, with optional roll/pitch/yaw or quaternion orientation, and wait until motion completes.

Instructions

Straight-line move of end_link to (x, y, z) m in the base frame. Orientation: roll/pitch/yaw in degrees (URDF fixed-axis; missing angles keep the current value) or quat [w, x, y, z]; omit both to keep the current orientation. 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": {
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "move_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
zYes
quatNo
yaw_degNo
roll_degNo
pitch_degNo
speed_mpsNolinear speed, m/s (default 0.05)
timeout_sNo

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 present, the description carries the full burden and does disclose genuinely useful traits: the path is a straight line (not joint-space), "Blocks until done" flags synchronous, potentially long-running behavior, and the orientation omission rule is spelled out. It stops short of failure modes, timeout semantics, interaction with collision guard/e-stop, and whether control must be taken first — significant gaps for a motion command.

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?

Three tight sentences ordered as target → orientation → blocking behavior, with no repeated or filler wording. Every clause carries information the caller needs.

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 9-parameter motion primitive with no annotations, no output schema, and almost no schema descriptions, the description covers the core call semantics (frame, units, orientation modes, blocking) well. The remaining omissions — quat-vs-RPY precedence, timeout_s meaning, and required preconditions/error behavior — are the notable gaps, but the definition is broadly sufficient to invoke correctly.

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?

Schema coverage is only 11% (just speed_mps), so the description must compensate, and it does: it defines units (meters, degrees), the base frame, the quat ordering [w, x, y, z], URDF fixed-axis convention, and the keep-current semantics for omitted angles and for omitting both orientation forms. It does not resolve the ambiguous case where both quat and roll/pitch/yaw are supplied, nor explain timeout_s.

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?

"Straight-line move of end_link to (x, y, z) m in the base frame" names a specific motion type, the moved entity, the target, and the reference frame. It is clear enough that an agent can distinguish it from a pose-based or relative move, though it never names move_to_pose or move_relative to make the distinction explicit.

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: absolute Cartesian target in the base frame, which the agent must contrast itself against siblings like move_to_pose and move_relative. There is no explicit when-to-use/when-not, and no stated preconditions such as needing control or an enabled robot before calling.

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