Skip to main content
Glama

doctor

Read-only

Diagnose applesauce version, enabled modules, and macOS permission states, then get the exact fix for a missing permission. Run it when a tool fails with PERMISSION_DENIED.

Instructions

Show the applesauce version, enabled modules, and the state of each macOS permission, with the exact step that fixes a missing one. Use it first when a tool fails with PERMISSION_DENIED.

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 observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description adds that this is a system-diagnostic that enumerates version, modules, permission states, and concrete fix steps. That tells the agent what it gets back and that running it is informational, without repeating annotation content. It does not discuss cost, latency, or whether remediation text is static advice vs. an executable action.

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 sentences: the first front-loads what is reported, the second gives the trigger condition. No filler, no restatement of the tool name, and the remediation detail is folded efficiently into the first sentence.

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?

For a zero-parameter, read-only diagnostic with no output schema, the description covers what it returns (version, modules, permission states, fix steps) and when to reach for it. Minor gaps remain around output format/structure and whether the "exact step" is guidance text only, but an agent has enough to call it correctly.

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 the 4 baseline applies. The description correctly implies no configuration is needed to run it, adding nothing misleading about inputs.

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?

Uses a specific verb ("Show") against three concrete resources: the applesauce version, enabled modules, and per-permission macOS state, plus the remediation step for any missing permission. That is unmistakably a diagnostics tool, easily separated from the note/mail/calendar/reminder siblings.

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?

"Use it first when a tool fails with PERMISSION_DENIED" gives an explicit trigger and sequencing (first). It does not state when this tool is unnecessary (e.g., after permissions are already confirmed working), so it stops short of full when/when-not guidance.

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