Garmin Connect IQ Simulator MCP Server

Overview Schema Source Related Servers Discussions Admin

swipe_screen

Simulate a cardinal-direction touch swipe on the Garmin watch display to navigate pages or trigger back/exit actions while respecting device gesture thresholds.

Instructions

Synthesize a touch drag gesture on the watch display in a cardinal direction ('up', 'down', 'left', 'right'), adhering to device gesture thresholds.

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": {
      "direction": "<direction>"
    },
    "name": "swipe_screen"
  }
}

Input Schema

Name	Required	Description
`wait_ms`	No	Milliseconds to wait after swipe before capturing screenshot (default: 350)
`device_id`	No	Device profile ID (defaults to active device)
`direction`	Yes	Direction of swipe gesture: 'up' (next page), 'down' (previous page), 'right' (back/exit), 'left'
`capture_after`	No	Whether to capture a screenshot after swiping (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations present, the description carries the full burden. It adds useful context by saying the gesture adheres to device gesture thresholds, but it omits side effects such as the default screenshot capture, the post-swipe wait, and whether the device must be booted or a device selected first.

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 with no wasted words; the action, target, and constraints appear immediately. Nothing is buried or repeated unnecessarily.

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 four-parameter input tool with a fully documented schema and no output schema, the definition covers the core behavior. The remaining gap is that it doesn't say what the caller gets back, especially since a screenshot is captured by default, leaving the return expectation to be inferred from sibling tools.

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 coverage is 100%, so all four parameters are already documented, including the directional mappings in the enum description. The prose behind the description only restates the cardinal directions and adds no syntax or behavioral meaning beyond what the schema already supplies.

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 and resource: 'synthesize a touch drag gesture on the watch display' with cardinal directions. It is clear what the tool does, but it never names or differentiates itself from nearby siblings like tap_screen or hold_screen, so an agent must infer that a swipe is a directional drag rather than a tap.

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 the gesture nature: use when a cardinal swipe is needed rather than a tap or button press. However, there are no explicit when-to-use or when-not-to-use instructions and no mention of the sibling alternatives that handle taps, holds, or screenshots.

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