Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

send_key

Sends a named key or virtual key code to the Connect IQ simulator window, with optional hold timing, post-press screenshot capture, and change/no-op assertions.

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')
expectNoAssert the outcome: 'change' fails with E_NO_CHANGE when the screen is identical, 'noop' fails with E_UNEXPECTED_CHANGE when it differs
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)
settle_msNoMilliseconds to wait before the after-capture used for the receipt (default: 400)
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 provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the send itself. It does not mention that the tool waits and captures screenshots, produces a change receipt, has side effects on simulator state, or requires an active window — details only inferable from parameter names in the schema.

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 naming the action, the input forms, the examples, and the target window. There is no filler or redundancy.

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

Completeness2/5

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

With eight parameters, no annotations, and no output schema, the definition needs to explain prerequisites, side effects, and what is returned (receipts, screenshots). None of that is present, leaving an agent to reconstruct behavior from parameter names alone.

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 eight parameters (expect, hold_ms, wait_ms, settle_ms, capture_after, device_id, key_code) are already documented in the schema. The description only restates the key/key_code inputs and adds no timing, assertion, or capture semantics.

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 and resource — send a virtual key code or named key to the Connect IQ simulator window — and lists valid key names. It does not distinguish the tool from siblings such as press_button, press_button_sequence, hold_screen, or act_on_ui, so an agent cannot tell from the text alone which input mechanism applies.

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?

No when-to-use guidance is given: nothing says when to prefer key events over press_button or hold_screen, nor any prerequisite such as the simulator needing to be running or focused. The only implicit signal is the mention of the simulator window.

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