Skip to main content
Glama

diagnose_slam

Diagnoses running SLAM systems by detecting map stalls, lost tracking, odometry drift, and missing loop closures, returning read-only findings for troubleshooting.

Instructions

Watch a running SLAM (slam_toolbox, Cartographer, RTAB-Map, ORB-SLAM3) and report map stalls, lost tracking, odometry drift and missing loop closures. Read-only. Uses slam_doctor.

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

Input Schema

NameRequiredDescriptionDefault
nsNo
secondsNo
domain_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 earn credit for declaring 'Read-only' and noting the slam_doctor dependency. However, it omits that the call presumably blocks for the `seconds` window (default 8), what environment/ROS domain it must attach to, or what the report looks like — significant for a live-monitoring tool that samples a running system.

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 short sentences, front-loaded with the detection targets and followed by the read-only guarantee, with no filler. The trailing 'Uses slam_doctor' is slightly cryptic but does convey a dependency.

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 enumerated failure modes partially compensate for the lack of an output schema, and 'Read-only' covers the safety profile. But with three undocumented parameters, no annotations, and no explanation of the sampling/blocking behavior, an agent cannot confidently construct 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% for all three parameters (ns, seconds, domain_id), and the description adds no meaning for any of them. A reader must infer that `seconds` is a sampling window and that `ns`/`domain_id` are ROS namespace and domain conventions, which is not stated anywhere.

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 gives a specific verb and resource ('Watch a running SLAM') and enumerates exactly what it reports: map stalls, lost tracking, odometry drift, missing loop closures. It also scopes itself to SLAM middleware (slam_toolbox, Cartographer, RTAB-Map, ORB-SLAM3), which implicitly separates it from diagnose_nav2/diagnose_perception, but it never names a sibling or states an explicit boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Watch a running SLAM' hints at the prerequisite that a SLAM stack is already running, but there is no statement of when to prefer this over diagnose_robot, diagnose_nav2, or ros_graph, and no exclusions or failure-case guidance. An agent has to infer the routing decision entirely.

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