Skip to main content
Glama
rebot-mcp

rebot-mcp

Official

get_state

Retrieve the reBot arm's current safety, fault, torque, lease, joint, end-link pose, gripper, and latest action state without acquiring a lease.

Instructions

Arm state: safety_state, fault, torque, lease, joints, end_link pose (host FK), gripper, latest action. No lease needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses one important behavioral fact (no lease/control acquisition required) and names what is returned, but never states that the operation is read-only and non-mutating, nor anything about latency or freshness of the state.

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 telegraphic sentence with no filler, and the most decision-relevant fact ('No lease needed') is placed at the end where it is still short enough to be read. Slight cost from the dense comma-list style and unexplained abbreviations like 'host FK'.

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?

With no output schema, the description must enumerate return content, and it does so fairly comprehensively (safety, fault, torque, lease, joints, pose, gripper, latest action). Gaps remain on field formats and value ranges, but for a zero-parameter read tool this is close to sufficient.

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 there is nothing for the description to disambiguate; baseline 4 applies. The list of state fields is return-value information, not parameter semantics.

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

Purpose3/5

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

The description is a noun phrase ('Arm state: ...') listing returned fields rather than stating a verb like 'get' or 'read'. The enumerated fields (safety_state, fault, torque, joints, gripper) make the resource identifiable and distinguish it from collision_guard_status or describe_safety, but the purpose is implied rather than stated.

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 real usage hint: it tells the agent this call can be made without take_control first, which is meaningful against the take_control/release_control siblings. However, there is no explicit when-to-use guidance and no statement of when another sibling (e.g. collision_guard_status) would be preferable.

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