Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

save_pose

Stores the robot arm's current joint positions under a named pose, replacing any existing pose with that name and persisting it on the device for later recall.

Instructions

CONFIGURATION CHANGE: save the arm's current joint positions under a name (letters, digits, _ and -, max 64), replacing a pose with that name. Move the arm there first (the user can hand-guide it or use the cockpit). Persisted on the device. Needs capability 'poses'.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/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 substantial work: it discloses overwrite semantics ('replacing a pose with that name'), persistence ('Persisted on the device'), and a required capability ('poses'). It omits error/return behavior and what happens if the capability is absent, keeping it from a 5.

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?

Front-loaded with a 'CONFIGURATION CHANGE:' marker that instantly signals mutation, then packs naming rules, precondition, persistence, and capability into three tight sentences. No wasted phrasing.

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 single-parameter mutation tool with no annotations and no output schema, this covers the decision-relevant facts: precondition, naming constraints, overwrite behavior, persistence, and auth capability. Only the failure modes and result of the call are left implicit, which is a minor gap given the tool's simplicity.

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

Parameters5/5

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

Schema description coverage is 0% — the only schema hint is the title 'Name' — so the description must compensate, and it does: allowed charset (letters, digits, _ and -), a 64-character max, and the uniqueness/overwrite consequence of reusing a name. Essentially no ambiguity remains about what to pass.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'save the arm's current joint positions under a name' — plus the replace-on-collision effect. An agent can distinguish this from list_poses or move_to_pose purely from the text.

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

Usage Guidelines4/5

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

Gives the essential precondition ('Move the arm there first') and two concrete ways to do so (hand-guide or cockpit), which is the real usage guidance for a save-current-state tool. It stops short of naming sibling tools or stating when-not-to-use (e.g., checking existing names first).

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