Skip to main content
Glama

diagnose_robot

Checks the ROS 2 graph to detect active stacks and runs applicable diagnostics in parallel, returning one merged, read-only verdict with errors first for troubleshooting a robot that will not move.

Instructions

Start here. Looks at the ROS graph, detects which stacks are present (Nav2, a ros2_control or MoveIt arm, SLAM, cameras), runs every doctor that applies in parallel and returns one merged verdict, errors first, each finding tagged with its source. Good for mobile manipulators. 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_robot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nsNo
secondsNo
domain_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden itself and does so: it declares 'Read-only', states that doctors run in parallel, and specifies result ordering (errors first) with source tagging per finding. It stops short of disclosing cost or latency — nothing says how long a full sweep takes or how the `seconds` budget affects thoroughness.

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?

Four short clauses, front-loaded with the entry-point signal and generalizing outward to stack detection, execution model, and return shape. No filler and no restatement of the tool name.

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

Completeness3/5

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

The description compensates well for the absent output schema by describing the merged verdict's ordering and source tagging. However, with zero annotation coverage and 0% parameter documentation, an agent is left guessing the effect of `seconds` and `domain_id` on a tool that fans out across many subprocesses.

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% and the description mentions none of the three parameters, so `ns`, `seconds`, and `domain_id` remain entirely unexplained — an agent cannot tell that `ns` scopes the ROS namespace, that `seconds` is a collection/timeout budget, or that `domain_id` selects a DDS domain. It only vaguely implies ROS namespacing through the graph context.

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?

The description gives a concrete verb chain — inspect the ROS graph, detect present stacks, run all applicable doctors in parallel, merge into one verdict — so an agent knows exactly what it does and how it differs from the narrower diagnose_arm/diagnose_nav2/diagnose_slam siblings. The opening 'Start here' plus the named stack families (Nav2, ros2_control/MoveIt, SLAM, cameras) fixes its scope.

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?

'Start here' and 'Good for mobile manipulators' give a clear entry-point signal and a target scenario. There are no exclusions or explicit pointers to the per-stack diagnose_* siblings for follow-up drill-down, so the when-not guidance is only implied.

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