Skip to main content
Glama

doctor

Run a self-diagnostic to check Python dependencies, API keys, browser launchability, database, and guard state when a tool misbehaves. Shows keyless vs key-gated providers and where case data lives.

Instructions

Self-diagnostic: python deps, API keys, browser, database, and guard state.

Run this first when a tool behaves unexpectedly. Shows which providers are keyless vs key-gated, whether Chromium is launchable, and where case data lives.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description must carry the full burden. It discloses what the diagnostic reports (keyless vs key-gated providers, Chromium launchability, case data location), which is genuine value. However, it never states that the operation is read-only/non-mutating, whether it requires network or auth, or how long it takes — meaningful gaps for a no-annotation tool.

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?

Three tight sentences, front-loaded with the identity of the tool, with the action trigger placed early. Minor redundancy between "API keys" in the list and the later "keyless vs key-gated" clause, but the elaboration adds real information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must indicate what comes back — it does, by naming the five state categories and the specific questions answered (keyless vs key-gated, Chromium launchable, case data location). Absent only an explicit statement of read-only behavior and output shape (structured vs prose).

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, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies no inputs are needed.

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+resource ("Self-diagnostic") and enumerates the exact subsystems it inspects: python deps, API keys, browser, database, guard state. This is clearly distinct from the sibling data-collection tools (dns_lookup, breach_check, browser_open), none of which are diagnostic in nature.

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?

"Run this first when a tool behaves unexpectedly" gives an explicit trigger condition, which is more than most siblings offer. It does not name alternatives or when-not-to-use, but for a first-line troubleshooting tool no sibling competes for that role.

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