Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

press_button_sequence

Run ordered simulator button presses with configurable delays, then capture the final watch screen to verify app behavior.

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

NameRequiredDescriptionDefault
stepsYesList of button press steps to execute in sequence
expectNoAssert the outcome: 'change' fails with E_NO_CHANGE when the screen is identical, 'noop' fails with E_UNEXPECTED_CHANGE when it differs
isolatedNoLaunch on a hidden desktop when the simulator is not running (default: true on Windows)
device_idNoDevice profile ID (defaults to active device)
settle_msNoMilliseconds to wait before the after-capture used for the receipt (default: 400)
capture_afterNoWhether to capture a screenshot after sequence completes (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses ordering, configurable delays, and final-screen capture, which is genuinely useful. However, it omits what happens if a step fails mid-sequence (does it abort?), how the returned receipt is shaped, and any environment requirements for launching the simulator.

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 sentence that front-loads the action and ends with the observable outcome. There is no filler and nothing that could be cut without losing meaning.

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 six-parameter mutation-style tool with no annotations and no output schema, the description covers the core behavior and the post-capture outcome. It falls short only on sequencing failure behavior and the shape of the returned receipt, which an agent would otherwise have to discover by calling it.

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 every parameter including defaults and error codes. The description only echoes two of them ('configurable delays', 'capturing the final watch screen') and adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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') and implies the distinction from the singular press_button sibling via 'sequence'. It is clear what the tool does, though it never explicitly names press_button as the single-press alternative.

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: the word 'sequence' and 'in order' suggest multi-step flows rather than a single press. There is no explicit statement of when to prefer this over press_button or act_on_ui, and no guidance on when the expect/isolated options should be set.

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