Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

debug_command

Send raw commands to the Garmin simulator's in-app debug channel to inspect state, seed data, set premium, list decks, map, time, phone, or reset the app during testing.

Instructions

Send a raw command to the in-app debug channel. Verbs: ping, state, seed, premium, deck_list, list, map, time, phone, reset; arguments are semicolon-free strings.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "verb": "<verb>"
    },
    "name": "debug_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNoPositional arguments after the verb
verbYesCommand verb, for example state
timeout_msNoTimeout in milliseconds (default: 10000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It hints at power with 'raw command' and lists mutating verbs (seed, premium, reset), but never states that these change state, may be irreversible, or require anything special; 'reset' in particular has no warning about destruction.

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?

Two sentences, front-loaded with the purpose, no filler. The verb list is a dense run-on, but every element is informative.

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?

For a no-annotation, no-output-schema tool that accepts arbitrary raw commands, the definition omits the critical mapping of which arguments each verb expects and what each verb returns or affects. The verb inventory is helpful but insufficient to call it confidently.

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?

Schema coverage is already 100%, so the baseline is 3, but the description adds real meaning: it enumerates accepted verb values that the schema only exemplifies ('for example state') and adds a constraint not present in the schema, namely that arguments must be semicolon-free strings.

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 action and target: 'Send a raw command to the in-app debug channel.' This is clear, but it does not explain how it differs from closely named siblings such as debug_ping or debug_status, leaving the agent to guess which entry point to use.

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?

The verb list implies what the tool can do but never says when to prefer it over debug_ping, debug_status, reset_state, or phone_message. No when-not-to-use or prerequisites are given.

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