Garmin Connect IQ Simulator MCP Server

Overview Schema Source Related Servers Discussions Admin

run_app

Run a compiled Monkey C executable on the active Garmin simulator device and stream runtime logs to debug app behavior.

Instructions

Push and run a compiled Monkey C executable (.prg) on the active device in the simulator using monkeydo, and stream logs.

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": {
      "prg_path": "<prg_path>"
    },
    "name": "run_app"
  }
}

Input Schema

Name	Required	Description
`wait_ms`	No	Milliseconds to wait for app launch and initial log output (default: 2500)
`prg_path`	Yes	Path to the compiled executable .prg file
`device_id`	No	Garmin device ID to run on (defaults to active device)
`capture_after`	No	Whether to capture and return an initial watch screenshot after launching (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A3.5/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose real behavior beyond the name: the artifact is pushed to the device, launched via monkeydo, and logs are streamed, which tells the agent this is a side-effecting launch operation. It does not say whether the call blocks until the app exits, whether the logs are returned in the response or streamed elsewhere, or what happens if an app is already running.

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 front-loaded sentence with the action verb first and no redundant restatement of the title or schema. Every clause ('compiled .prg', 'active device', 'using monkeydo', 'stream logs') adds distinct information.

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 four-parameter launch tool with no annotations and no output schema, the description should clarify the return contract, since 'stream logs' is ambiguous about whether log text comes back in the response. Prerequisites (simulator running, active device set, app built) are also unaddressed, leaving meaningful gaps for an agent deciding whether it can call this now.

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 all four parameters (prg_path, device_id, wait_ms, capture_after) are already documented in structured form. The description adds only the 'active device' default framing for device_id and the log-streaming context tied to wait_ms; it contributes no new syntax or format detail.

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 gives a specific verb pair ('Push and run') and a specific resource ('compiled Monkey C executable (.prg)'), plus the mechanism ('monkeydo') and target ('active device in the simulator'). This clearly separates it from build_app (compiles) and stop_app (stops), though it never names a sibling explicitly.

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: 'on the active device in the simulator' hints that a simulator and active device must exist, and 'compiled ... .prg' hints that build_app must run first, but neither prerequisite nor any when-not condition (e.g., app already running, use stop_app first) is stated.

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