Garmin Connect IQ Simulator MCP Server

Overview Schema Source Related Servers Discussions Admin

get_screenshot

Captures screenshots of the Garmin Connect IQ simulator in screen, bezel, or annotated debug view to inspect app UI, layout, and controls.

Instructions

Capture a screenshot of the Connect IQ simulator. Supports watch display crop ('screen', 1:1 pixel mapping), full window with bezel ('bezel'), or annotated debug view with button hitboxes and coordinate grid ('annotated').

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

Input Schema

Name	Required	Description
`view`	No	Screenshot view mode: 'screen' crops to watch display; 'bezel' captures device bezel; 'annotated' composites SVG debug overlay (default: 'screen')
`device_id`	No	Device profile ID (defaults to active device)
`save_path`	No	Optional file path on disk to save the PNG image

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A3.8/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 well on what each mode produces, but never states that the simulator must be running, what happens on failure, or how the image is returned versus written to disk — relevant for a capture tool whose result the agent must then consume.

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 core action front-loaded and the mode enumeration following; every clause adds information. It is slightly long for one sentence but contains no filler.

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?

With no output schema and no annotations, the description should say more about the return value (inline image vs. saved PNG path) and any precondition such as an active simulator session. The three optional parameters are well covered, so the gap is limited but real.

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 100%, so the baseline is 3; the description earns a point above baseline by adding meaning the schema lacks, specifically the 1:1 pixel mapping of 'screen' and the concrete contents of the 'annotated' overlay (button hitboxes and coordinate grid).

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?

States a specific verb and resource ("Capture a screenshot of the Connect IQ simulator") and then enumerates the three distinct output modes, which lets an agent distinguish this from siblings like inspect_ui or recognize_image_text without opening the schema.

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 view-mode descriptions imply when each variant is appropriate (crop for pixel-accurate display, bezel for full device look, annotated for debugging hitboxes), but there is no explicit when-to-use/when-not guidance and no mention of the obvious alternatives (recognize_image_text for OCR, inspect_ui for widget hierarchy).

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