Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

launch_simulator

Starts the Garmin Connect IQ simulator, by default on a hidden Windows desktop to keep button input from changing your foreground window; set wait time and visible desktop as needed.

Instructions

Launch the Garmin Connect IQ simulator, by default on a hidden Windows desktop where button input does not change your foreground window.

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

Input Schema

NameRequiredDescriptionDefault
wait_msNoMaximum milliseconds to wait for the simulator window and TCP port 1234 (default: 25000 isolated, 15000 normal)
isolatedNoRun on a hidden desktop (default: true on Windows). Set false to use the visible desktop and the focus lease.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully explains the hidden-desktop default and why it matters (button input won't steal focus), but omits idempotency behavior, failure modes (e.g., port 1234 in use), and what a successful launch returns.

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 well-formed sentence that front-loads the action and then the most consequential default behavior. Nothing is redundant or wasted.

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 launch tool with no annotations and no output schema, the description covers the isolation behavior but leaves the agent guessing about idempotency, failure handling, and whether any handle is returned. Adequate but with clear gaps.

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 description coverage is 100%, so wait_ms and isolated are already fully documented, including their defaults. The description only echoes the isolated default, adding no syntax or edge-case detail beyond the 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?

States a specific verb and resource ('Launch the Garmin Connect IQ simulator'), which cleanly separates it from siblings like terminate_simulator and simulator_status. It does not explicitly name an alternative, but the action itself is unambiguous.

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 implied by 'Launch' — an agent will understand this starts the simulator. However, there is no guidance on preconditions (e.g., whether to check simulator_status first) or on what to do if an instance is already running.

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