Skip to main content
Glama

ros_graph

Lists ROS 2 nodes and topics visible on a domain (read-only) to identify the correct domain or namespace when nothing appears in a doctor report.

Instructions

List the nodes and topics visible on a ROS domain (read-only). Use it first when a doctor reports that nothing is visible, to find the right domain or namespace.

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

Input Schema

NameRequiredDescriptionDefault
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 provided, so the description carries the full burden. It does disclose that the operation is read-only and that it lists nodes and topics, which is useful safety context. However, it says nothing about what happens when the domain_id is invalid, whether results are live or cached, or how the output is shaped, and with no output schema those gaps matter.

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?

Two short sentences, the purpose front-loaded and the usage cue second. Every clause carries information and there is no filler.

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?

For a one-parameter discovery tool with no annotations and no output schema, the description covers intent and safety but leaves the parameter semantics and the return shape unaddressed. An agent knows when to call it but not how to interpret domain_id or what the listing contains.

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 single parameter domain_id is undocumented in the schema. The description only hints at it through 'on a ROS domain' and 'find the right domain or namespace'; it never explains what domain_id means, what the null default implies, or what format it takes. The description does not compensate for the coverage gap.

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?

States a specific verb and resource: 'List the nodes and topics visible on a ROS domain.' That is concrete and distinguishes it from the diagnose_* siblings, which target specific subsystems rather than raw discovery. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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?

Gives a real trigger condition: 'Use it first when a doctor reports that nothing is visible.' That is actionable routing guidance an agent can apply. It does not state when not to use it or name a follow-up alternative, so it falls short of the 5 bar.

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