Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

move_relative

Move the robot arm's end effector by relative translations and rotations in base, tool, or camera frames, then wait until the motion completes.

Instructions

Relative move of end_link. frame: base (base axes), tool (end_link axes) or camera (x right, y down, z forward along the view; dpitch > 0 looks down, dyaw > 0 looks right; level keeps the image level, default true). Translations in m (each <= 0.30), rotations in degrees (each <= 90), centred on end_link. 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": {
      "frame": "<frame>"
    },
    "name": "move_relative"
  }
}

Input Schema

NameRequiredDescriptionDefault
dxNo
dyNo
dzNo
frameYes
levelNo
dyaw_degNo
droll_degNo
speed_mpsNolinear speed, m/s (default 0.05)
dpitch_degNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so well: it discloses per-axis magnitude limits, that the motion is centred on end_link, the camera axis conventions and sign meanings for dpitch/dyaw, the level default, and that the call blocks until completion. It omits failure behaviour (collisions, out-of-range handling) and whether control ownership or an enabled state is required, which matters 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph that leads with the purpose, then layers frame semantics, limits, and blocking behaviour. Parenthetical clauses are information-rich rather than redundant, though the camera-frame aside is packed tightly enough to be slightly hard to parse.

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?

Covers the geometric semantics thoroughly for a 9-parameter motion tool, but with no annotations and no output schema it should also say what happens on failure or limit violation and whether take_control/enable are prerequisites. Those operational gaps leave an agent guessing before an actual move.

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 largely does: it defines the frame enum axes, the units and limits for translations and rotations, the sign conventions for dpitch/dyaw, and the level flag's default. droll_deg and the per-frame mapping of dx/dy/dz are left implicit, and speed_mps is only documented in the schema.

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 and resource ('Relative move of end_link'), and the word 'relative' implicitly separates it from the absolute-move siblings move_to/move_to_pose. No sibling is named explicitly, so the differentiation is left to inference.

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?

Gives useful context for choosing a frame (base/tool/camera) and notes it 'Blocks until done', which hints at synchronous use. But it never states when to prefer this over move_to or move_to_pose, nor any preconditions such as needing to hold control.

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