Garmin Connect IQ Simulator MCP Server

Overview Schema Source Related Servers Discussions Admin

press_button_sequence

Runs an ordered sequence of button presses with configurable delays, then captures the final watch screen for automated Garmin Connect IQ app testing.

Instructions

Execute a sequence of button presses in order with configurable delays, capturing the final watch screen.

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": {
      "steps": "<steps>"
    },
    "name": "press_button_sequence"
  }
}

Input Schema

Name	Required	Description
`steps`	Yes	List of button press steps to execute in sequence
`device_id`	No	Device profile ID (defaults to active device)
`capture_after`	No	Whether to capture a screenshot after sequence completes (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?

With no annotations provided, the description carries the full behavioral burden. It discloses sequential execution, configurable delays, and final screen capture, but does not explain device-state side effects, failure handling, or whether the interaction is reversible.

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?

The description is a single front-loaded sentence with no filler. Every clause contributes useful context about ordering, delays, and final capture.

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?

The tool is moderately complex: it accepts a nested steps array and has no annotations or output schema. The description covers the main action and screenshot behavior, but leaves gaps around return values, failure behavior, and active-device selection context.

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 the schema already documents steps, device_id, and capture_after in detail. The description adds only a high-level reference to sequential steps, delays, and final capture, without meaningfully expanding parameter semantics beyond the schema.

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 specific verb and resource: execute a sequence of button presses in order, with delays and a final screen capture. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling press_button tool.

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 implied by 'sequence' versus the sibling single-press tool, but the description does not explicitly say when to use this tool instead of press_button or tap_screen. There are no exclusions or prerequisite guidance.

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