Skip to main content
Glama

proteus_doctor

Read-only

Reports capability-specific health for Proteus MCP, distinguishing installed components from verified working status so you know what is operational before relying on it.

Instructions

Report capability-specific health. Installed is not verified working.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false with openWorldHint=false, so safety is covered and the bar is lower. The description adds one genuine behavioral insight — that installation is not equivalent to a working capability — but does not disclose what gets probed, whether it is slow or side-effect-free in practice, or how the health verdict is expressed.

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 very short sentences with zero filler, and the purpose statement is front-loaded ahead of the caveat. Nothing could be removed without losing meaning.

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?

There is no output schema, so the description carries the burden of explaining what a health report looks like — and it does not, leaving the agent unsure what comes back (a list of capabilities with statuses? a single pass/fail?). For a diagnostic tool whose entire value is its output, the definition is adequate but thin.

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 per the baseline this scores 4; there is nothing for the description to disambiguate beyond the empty schema.

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 uses a specific verb ("Report") tied to a specific resource ("capability-specific health"), and the second sentence clarifies the semantics of what is being reported. It is clearly distinct from sibling tools, which are all editing/build/inspection operations, but it never says which capabilities are probed or what the report contains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: "Installed is not verified working" hints that this should be called to confirm functionality rather than mere presence, which suggests using it after setup or when something misbehaves. There is no explicit when-to-use/when-not guidance and no named alternative, so the agent must infer the trigger condition.

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