Garmin Connect IQ Simulator MCP Server

Overview Schema Source Related Servers Discussions Admin

set_active_device

Sets the active Garmin device ID so subsequent simulator commands, button presses, touch gestures, and screenshot cropping target the selected device.

Instructions

Set the active Garmin device ID for subsequent simulator commands, button presses, touch gestures, and screenshot cropping.

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": {
      "device_id": "<device_id>"
    },
    "name": "set_active_device"
  }
}

Input Schema

Name	Required	Description	Default
`device_id`	Yes	Target device ID (e.g. 'fenix847mm', 'venu3', 'fr965', 'epix2pro47mm')

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?

With no annotations, the description carries the full burden, and it does useful work by disclosing that this mutates persistent session state affecting later calls. It omits what happens with an unknown/invalid device ID (error vs. silent fallback), whether the setting persists across simulator restarts, and whether a default device exists.

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?

One sentence, front-loaded with the action and the state change, then the list of downstream effects. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter, non-output tool this covers the essential purpose and side effect. The remaining gap is discoverability of valid IDs and invalid-ID behavior, which matters because the tool's whole job is validating an identifier.

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% and the schema already supplies concrete ID examples ('fenix847mm', 'venu3', 'fr965'), so the description adds little beyond confirming the parameter designates which device becomes active. Baseline 3 is appropriate when the schema does the explanatory work.

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 ('Set') and resource ('active Garmin device ID') plus the downstream scope it affects (simulator commands, button presses, touch gestures, screenshot cropping). It implicitly separates itself from list_devices, but never names that sibling as the discovery counterpart, so sibling differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when to call it: before any command, gesture, or screenshot operation, since those depend on the active device. There are no exclusions or explicit 'if you don't know the ID, call list_devices first' routing, which keeps it below a 5.

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