Skip to main content
Glama

read_diagnostics

Read-onlyIdempotent

Retrieve recent diagnostic messages for a specified robot, oldest first, with an optional limit to inspect its latest health or fault status.

Instructions

Most recent diagnostic messages of a robot, oldest first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "robot_id": "<robot_id>"
    },
    "name": "read_diagnostics"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
robot_idYesRobot id, e.g. amr_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely new behavior — results are recent-only and returned oldest-first — which matters for interpreting output. It does not say whether an empty result means no faults, how far back 'recent' reaches, or whether messages are ever truncated.

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?

One short sentence, front-loaded with the resource and immediately followed by the two scoping facts. Nothing extraneous.

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 simple two-parameter read tool with a full safety annotation set, the description covers what is returned and in what order. It leaves the practical questions — default volume, meaning of an empty list, severity of the messages — unanswered, which an agent diagnosing a robot would care about.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: robot_id is documented with an example, while limit is only bounded by default/min/max. The description's 'most recent ... oldest first' implicitly explains what limit truncates and in which direction, which is useful, but it never states that limit is a message count.

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 names the resource precisely (diagnostic messages of a robot) and adds scope (most recent) and ordering (oldest first). It is not a verb-led statement and does not explicitly distinguish itself from siblings like get_robot_state, but the resource is specific enough that an agent can tell what it retrieves.

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?

There is no when-to-use guidance, no mention of what this is for (fault triage, health checks), and no alternatives or preconditions. The agent must infer usage entirely from the resource name.

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