Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

list_poses

Retrieve saved reBot arm poses with names, joint positions, and TCP data to review or reuse configured arm positions.

Instructions

Saved poses: {count, poses[{name, positions, tcp}]}. No lease needed. Needs armd capability 'poses'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return payload structure, that no lease is required, and that the 'poses' armd capability is a prerequisite. It stops short of stating error behavior when the capability is absent or what an empty result looks like.

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?

Three short clauses, front-loaded with the resource and payload, followed by two operational constraints. Nothing is wasted, though the payload notation is slightly cryptic without context on field meaning (e.g., positions vs tcp).

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 parameterless read tool with no output schema, the description effectively substitutes for a return schema and covers the key preconditions. Missing only edge-case detail such as behavior on error or empty pose lists.

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 baseline is 4. There is nothing for the description to disambiguate, and it correctly adds no parameter noise.

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?

Names the resource precisely ('Saved poses') and the inline return shape {count, poses[{name, positions, tcp}]} makes clear this is a read that enumerates stored poses. It does not explicitly contrast with the sibling save_pose, so an agent must infer the read-vs-write split from the name alone.

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?

'No lease needed' is a genuinely useful usage signal, telling the agent this can be called without take_control, unlike motion siblings. However, there is no explicit statement of when to call it (e.g., to discover a pose name before move_to_pose) or when not to.

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