Skip to main content
Glama
Sign In
Garmin Connect IQ Simulator MCP Server

Garmin Connect IQ Simulator MCP Server

by keponer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

send_key

Sends named or virtual key presses to the Garmin Connect IQ simulator window to automate navigation and input testing, with optional hold duration and post-press screenshot capture.

Instructions

Send a platform virtual key code or named key ('enter', 'esc', 'up', 'down', 'menu', 'space') to the Connect IQ simulator 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": "send_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoKey name or alias (e.g. 'enter', 'return', 'select', 'esc', 'back', 'up', 'down', 'menu', 'space')
hold_msNoKey hold duration in milliseconds (default: 80)
wait_msNoMilliseconds to wait after key press before capturing screenshot (default: 350)
key_codeNoPlatform virtual key code (Windows and macOS use different codes)
device_idNoDevice profile ID (defaults to active device)
capture_afterNoWhether to capture and return a screenshot after key press (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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, yet it discloses no behavioral traits: no prerequisite that the simulator must be running and an active device selected, no statement about the side effect of injecting a key event, and no mention that a screenshot is returned when capture_after is set. It only restates what the tool does at a high level.

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 front-loaded sentence with no wasted preamble. The inline key list is somewhat redundant with the schema's richer alias list, and the sentence omits the key_code form mentioned in the schema.

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 six-parameter tool with no annotations and no output schema, the definition is minimal but functional: the schema covers parameters, so the main gap is the absence of execution prerequisites and return-value expectations (screenshot capture behavior). It is adequate for a simple input-injection tool but leaves real operational questions unanswered.

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 six parameters including hold_ms, wait_ms, and capture_after are already documented in the schema. The description adds nothing about timing, device targeting, or key-code selection beyond repeating the named-key examples, so the schema does the heavy lifting.

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 states a concrete verb ('Send') and resource ('platform virtual key code or named key') and names the target, the Connect IQ simulator window. It does not explicitly distinguish itself from closely related siblings such as press_button, tap_screen, or trigger_menu_action.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says whether to prefer this over press_button (for hardware buttons) or trigger_menu_action, nor when a raw key_code is needed versus a named key. Usage must be inferred entirely from the description text and sibling names.

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

Deploy Server

Other Tools