Skip to main content
Glama

doctor

Read-onlyIdempotent

Check installation status, persisted setup, and actual tool, cluster, and background job receipts separately to diagnose configuration and execution problems.

Instructions

Inspect installation, persisted setup and actual tool/cluster/background receipts separately.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully carried by structured data. The description adds only the word 'separately', hinting the report is partitioned into distinct sections, but says nothing about scope of checks, cost, or side-effect-free verification semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single sentence with no filler, which is good, but the phrasing is compressed to the point of opacity ('receipts', 'separately' with no referent). Brevity here costs comprehension rather than earning it.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. Still, for a diagnostic entry point the description leaves the agent unsure what conditions should trigger it and what 'separately' means in practice.

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

Parameters4/5

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

The tool takes zero parameters and the empty schema makes that unambiguous, so there is nothing for the description to clarify about inputs. Baseline of 4 applies for a parameterless tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Inspect' plus three objects ('installation', 'persisted setup', 'tool/cluster/background receipts') signals a diagnostic tool, but 'receipts' is undefined jargon and the scope boundaries are fuzzy. An agent can guess this is a health/diagnostic check, but cannot precisely say what it verifies versus what it merely reports.

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 prerequisites, and no routing to alternatives. Siblings like connection_check, environment_verify, environment_capture, and check_run plausibly overlap with diagnostics, yet the description never tells the agent which to pick.

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