Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

doctor

Verifies the SDK, toolchain, device profiles, developer key, simulator window, occlusion, and session log so you can determine whether an app failure is caused by the app or the environment.

Instructions

Check the SDK, toolchain, device profiles, developer key, simulator window, occlusion and session log before blaming an app failure on the app.

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
project_dirNoProject directory used to look for a developer key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It usefully discloses the breadth of inspection (seven named subsystems) and the fact that a developer key is looked up in the project directory, implying environment-dependent behavior. It does not say whether checks are read-only or side-effecting (e.g. launching a simulator), how long a sweep takes, or what a result looks like.

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?

A single dense sentence with the check list front-loaded and the triggering situation last. No filler or repetition, though the closing clause is colored phrasing rather than a crisp usage rule.

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 should convey what the agent gets back from a diagnostic sweep — a list of failing checks, a health verdict, remediation hints — and it does not. Combined with silence on side effects for a tool that inspects simulator windows and sessions, a meaningful gap remains for a one-parameter tool.

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?

One optional parameter with 100% schema description coverage, so the schema already explains project_dir. The description never references the parameter or explains what omitting it does, so it adds nothing beyond the schema — baseline 3 applies.

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 verb is 'Check' and the resources are enumerated concretely: SDK, toolchain, device profiles, developer key, simulator window, occlusion, session log. That is far more specific than the bare name 'doctor' and lets an agent recognize it as a preflight/diagnostic sweep rather than a single-purpose probe like debug_ping. It stops short of stating what the tool produces (a report, pass/fail list), so not a 5.

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?

'before blaming an app failure on the app' implies the intended moment: when an app failure's cause is ambiguous. Usage is implied rather than stated as a rule, and no alternative sibling (e.g. debug_status, debug_ping, get_app_logs) is named or excluded.

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