Skip to main content
Glama

diagnose_nav2

Watches a running Nav2 stack to identify why a robot is not moving—stale TF, dead odom/scan, inactive lifecycle nodes, missing cmd_vel, or flapping goals—and returns read-only findings with hints.

Instructions

Watch a running Nav2 stack and name why the robot is not moving (stale TF, dead odom/scan, inactive lifecycle nodes, no cmd_vel, flapping goals ...). Read-only. Returns ok and findings with hints.

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_nav2"
  }
}

Input Schema

NameRequiredDescriptionDefault
nsNo
secondsNo
domain_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it declares 'Read-only', implies continuous observation of live state, and discloses the return contract ('ok and findings with hints'). It omits whether a running stack is required for a useful result and whether the observation window blocks the caller.

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?

Two compact sentences plus a parenthetical list, front-loaded with the core action and followed by the safety and return contract. The ellipsis-ended failure list is efficient rather than padded, though the parameter-less prose leaves the reader abruptly at the end.

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?

There is no output schema and no annotations, so the description must cover a live diagnostic across an unknown ROS environment; it gives a partial return contract and a good failure taxonomy but leaves all three inputs unexplained and does not say what happens when the stack is absent or still starting.

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% for three parameters, and the description mentions none of them — not the namespace scoping (`ns`), not the observation window (`seconds`), not the ROS domain (`domain_id`). The agent must infer that the watch duration is tunable and that the namespace selects which stack is inspected.

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 running Nav2 stack') and the exact question it answers ('name why the robot is not moving'), then enumerates the failure classes it detects (stale TF, dead odom/scan, inactive lifecycle nodes, no cmd_vel, flapping goals). This clearly separates it from a binary readiness check like nav2_ready and from the broader diagnose_robot.

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?

The trigger condition is explicit: a running Nav2 stack with a robot that is not moving. It does not state when NOT to use it (e.g. when the stack is not yet launched) or name an alternative for a simple up/down check, so the routing guidance is clear but incomplete.

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