Skip to main content
Glama

arm_ready

Verifies that a ros2_control arm can move now before motion commands are issued, returning ok only when the arm is ready.

Instructions

Pre-flight check for a ros2_control arm: ok only if it can move now.

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

Input Schema

NameRequiredDescriptionDefault
nsNo
moveitNo
secondsNo
domain_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 does disclose the meaningful behavioral trait of a boolean pass/fail criterion ('ok only if it can move now'), but says nothing about whether the check mutates state (spinning/activating controllers), whether it blocks for the timeout period, or what happens when the arm is not ready.

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?

A single well-formed sentence with the purpose and the pass condition front-loaded. Nothing is padded or repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and four fully undocumented parameters, the description does too little. It never clarifies whether the check is read-only or has side effects on the ros2_control controllers, nor what 'moveit' or 'domain_id' change about the check.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters (ns, moveit, seconds, domain_id), and the description explains none of them. The word 'now' faintly hints that the check is time-bounded, which loosely relates to 'seconds', but there is no explicit mapping to any parameter.

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?

The description names a specific verb and resource: a 'pre-flight check for a ros2_control arm', and defines the success criterion ('ok only if it can move now'). That is enough to distinguish it from diagnostic siblings like diagnose_arm, though it never names an alternative explicitly.

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?

The phrase 'pre-flight check' implies usage before commanding motion, but the description never states when to call it versus diagnose_arm or check_reach, nor what to do when the check fails. Usage is implied rather than specified.

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