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

tap_screen

Simulate a touchscreen tap on the Garmin simulator at pixel or normalized coordinates to test watch interactions and capture the resulting screen.

Instructions

Tap the watch touchscreen at specific display coordinates (X, Y) or normalized coordinates (0.0..1.0).

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "tap_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX coordinate: display pixels (0..width) or normalized ratio (0.0..1.0 if normalized: true)
yYesY coordinate: display pixels (0..height) or normalized ratio (0.0..1.0 if normalized: true)
wait_msNoMilliseconds to wait after tap before capturing screenshot (default: 350)
device_idNoDevice profile ID (defaults to active device)
normalizedNoWhether coordinates are normalized 0.0 to 1.0 (default: false)
capture_afterNoWhether to capture a screenshot after tapping (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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, and it discloses almost nothing beyond the action itself. It does not say the tap mutates app state and may trigger navigation, and it does not mention the post-tap screenshot capture behavior that the schema actually defaults to true — a meaningful side effect an agent should know about before calling.

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 that names the action and both coordinate interpretations, with no filler or redundancy. Nothing could be removed without losing information.

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 interaction tool with no annotations and no output schema, the description covers the core mechanic but leaves behavioral gaps: side effects on app state, capture-after behavior, and failure modes (off-screen coordinates, no active device). Adequate but not complete for a UI-driving mutation.

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 wait_ms, device_id, normalized, and capture_after defaults, are already documented in the schema. The description's mention of coordinate modes simply restates the schema rather than adding format rules or edge-case guidance, so the baseline of 3 applies.

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 ('Tap the watch touchscreen') and clarifies the two coordinate modes (pixels vs normalized 0.0..1.0). It is distinguishable from swipe_screen and hold_screen by the verb alone, but it never explicitly contrasts itself with those siblings or with act_on_ui.

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 at all: nothing says when a raw coordinate tap is preferable to act_on_ui, swipe_screen, or hold_screen, and no prerequisites (active device, app must be foregrounded) are mentioned. Usage is only inferable from the tool name.

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