Skip to main content
Glama

diagnose_arm

Diagnose why a ros2_control or MoveIt 2 arm won't move by identifying inactive controllers, silent joint_states, joint limits, stalled trajectories, or missing move_group. Read-only.

Instructions

Watch a ros2_control / MoveIt 2 arm and name why it is not moving (inactive controller, silent joint_states, joint at a limit, stalled trajectory, missing move_group ...). Read-only.

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

Input Schema

NameRequiredDescriptionDefault
nsNo
moveitNo
secondsNo
domain_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the key behavioral traits that it is observational only ('Read-only') and that it observes over a period ('Watch' plus the seconds param). It does not say whether the tool blocks for the full window, what permissions/topics it needs, or what a report contains, so an agent cannot predict side effects or duration precisely.

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 front-loaded sentence with the failure modes in parentheses and the safety property trailing; nothing is redundant and the scoping constraint comes before the detail.

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?

For a tool with four undocumented parameters, no annotations, and no output schema, the description omits too much: it never explains ns, domain_id, or moveit, and never indicates what the returned diagnosis looks like. The read-only and purpose information is good, but an agent still cannot confidently parameterize the call.

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, and the description only obliquely hints at two of them: 'Watch' implies the seconds observation window, and 'ros2_control / MoveIt 2' hints that moveit toggles MoveIt-specific checks. The ns and domain_id parameters get no meaning at all, leaving the agent to guess at namespace scoping and DDS domain selection.

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 ('Watch a ros2_control / MoveIt 2 arm and name why it is not moving') and enumerates the failure classes it distinguishes (inactive controller, silent joint_states, joint at a limit, stalled trajectory, missing move_group). This scopes it away from the broader diagnose_robot and other domain-specific diagnose_* siblings without opening a schema.

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 symptom list implies the situation to use it in (an arm that isn't moving), and 'Read-only' signals it is safe to run ad hoc. However there is no explicit when-not guidance, no mention of what to do if the arm is a non-ros2_control arm, and no reference to alternative diagnostics for related-but-different symptoms.

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