Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

tap_screen

Simulate a touchscreen tap at specified pixel or normalized X/Y coordinates to interact with Garmin simulator apps, with optional outcome assertions and post-tap screenshot capture.

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)
expectNoAssert the outcome: 'change' fails with E_NO_CHANGE when the screen is identical, 'noop' fails with E_UNEXPECTED_CHANGE when it differs
wait_msNoMilliseconds to wait after tap before capturing screenshot (default: 350)
device_idNoDevice profile ID (defaults to active device)
settle_msNoMilliseconds to wait before the after-capture used for the receipt (default: 400)
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.2/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 behavioral burden, yet it only restates the tap action. It does not disclose that the tool mutates device UI state, that it captures screenshots by default, that it waits (wait_ms/settle_ms) and produces a receipt, or that 'expect' can force failures such as E_NO_CHANGE.

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 the action first and the coordinate modes second; there is no filler or redundancy. It is short but every clause earns its place.

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?

This is an eight-parameter interaction tool with assertion semantics, timing controls, and screenshot capture, and it has no annotations and no output schema. The one-line description leaves the agent unaware of the receipt/capture behavior and the failure modes that 'expect' can trigger, which is a substantial gap for a state-mutating tool.

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 every one of the eight parameters is already documented in the input schema, including normalized, capture_after, expect, and the wait timings. The description echoes the pixel-vs-normalized coordinate distinction but adds no semantics beyond that baseline.

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 ('Tap the watch touchscreen') and clarifies the two coordinate modes (display pixels vs normalized 0.0..1.0). It is clearly distinguishable from hold_screen and swipe_screen by the discrete single-tap framing, though it never names those siblings explicitly.

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 only implied: a single-point tap. There is no guidance on when to prefer this over hold_screen, swipe_screen, press_button, or act_on_ui, and no mention of prerequisites such as needing an active device or a settled screen state.

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