Skip to main content
Glama

Doctor

doctor

Checks diagnostic health and configuration integrity of the Project Brain and MCP server to surface misconfigurations.

Instructions

Check the diagnostic health and configuration integrity of the Project Brain and MCP server.

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
pathNoProject root directory..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/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; 'Check' implies a safe read-only inspection, which is useful, but this is never stated outright. It also does not say whether the diagnostic can mutate or repair configuration, how long it takes, or that it only inspects the given project root — real concerns for a tool named 'doctor' that could plausibly attempt fixes.

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?

A single front-loaded sentence naming the object of inspection, with zero filler or repetition. Nothing in it is wasted or could be trimmed without losing content.

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 output schema documents what the diagnostic returns, which covers the biggest gap for a check-style tool. However, for a tool with no annotations and no required parameters, the description still omits whether the check is purely read-only, what it verifies, and when an agent should prefer it over project_info or project_dashboard.

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 100% and the single 'path' parameter is already documented as 'Project root directory,' so the schema carries the semantics. The description adds nothing about what the path scopes (which configuration files or brain state get checked), so it neither helps nor hurts beyond the baseline.

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 ('Check') and a specific resource ('diagnostic health and configuration integrity of the Project Brain and MCP server'), so the agent knows exactly what the tool inspects. It does not distinguish itself from nearby diagnostic-flavored siblings such as project_info, project_dashboard, or get_dev_mcp_profile, so an agent may hesitate between them.

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 explicit when-to-use guidance, no prerequisites (e.g., 'requires an initialized Project Brain'), and no mention of when not to use it. The word 'diagnostic' implies troubleshooting, but nothing routes the agent away from project_info or project_dashboard for overlapping needs.

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