Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

press_button

Simulate pressing a Garmin device bezel button—select, back, up, down, or menu—with short clicks or long holds, then return the updated watch screen for verification.

Instructions

Press a physical bezel button on the active Garmin device (e.g. 'select', 'back', 'up', 'down', 'menu'). Supports short clicks or long-press holds, and returns the updated 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": {
      "button": "<button>"
    },
    "name": "press_button"
  }
}

Input Schema

NameRequiredDescriptionDefault
holdNoPerform a long press (hold) instead of short click
buttonYesButton identifier or alias (e.g. 'select', 'enter', 'start', 'back', 'esc', 'up', 'down', 'menu')
expectNoAssert the outcome: 'change' fails with E_NO_CHANGE when the screen is identical, 'noop' fails with E_UNEXPECTED_CHANGE when it differs
methodNoInput synthesis method: 'mouse' clicks bezel hitbox center; 'key' sends macOS virtual keycode (default: 'mouse')
hold_msNoCustom hold duration in milliseconds (defaults to 1200ms for hold, 80ms for short click)
wait_msNoMilliseconds to wait after button press before capturing screenshot (default: 350)
device_idNoDevice profile ID to resolve button coordinates from (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 the button press (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It helpfully discloses that the tool returns the updated watch screen and that it mutates physical device state, but it omits failure behavior, error codes such as E_NO_CHANGE, and the fact that a screenshot capture happens by default.

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?

Two tight sentences, front-loaded with the action and resource, then the click/hold capability and the return value. No filler or restated naming.

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?

Given nine parameters, a device mutation, and no output schema or annotations, the description covers what it does and what it returns but leaves failure modes, assertion behavior, and post-press settling semantics entirely to the schema. Adequate but not complete for a tool of this complexity.

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 all nine parameters, including hold, expect, method, and timing values. The description echoes the button aliases and hold-vs-click distinction but adds no meaning beyond the schema, so baseline 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?

The description gives a specific verb and resource — 'Press a physical bezel button on the active Garmin device' — with concrete button examples. It does not differentiate itself from plausible siblings such as press_button_sequence, send_key, or hold_screen, so an agent cannot tell from the text alone which one to pick.

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?

It states a short click vs. long-press capability but gives no when-to-use guidance, no prerequisites, and no exclusions. An agent has no cue whether to use this versus press_button_sequence (for multiple presses) or send_key, which is a real misuse risk given the crowded sibling set.

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