Skip to main content
Glama
Garmin Simulator MCP
by dqclqn

wait_for_stable

Waits until two consecutive simulator captures are identical before screenshots or assertions, preventing mid-animation captures.

Instructions

Wait until two consecutive simulator captures are identical, so screenshots and assertions are not taken mid-animation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wait_for_stable"
  }
}

Input Schema

NameRequiredDescriptionDefault
settle_msNoInitial settle delay in milliseconds
timeout_msNoMaximum wait in milliseconds (default: 3000)
interval_msNoPoll interval in milliseconds (default: 150)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses the stability criterion (two identical consecutive captures) and the anti-animation rationale, but never states what happens on timeout, whether it errors or returns a boolean, or how polling interacts with settle_ms.

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?

One sentence, front-loaded with the core behavior and closed with the motivating rationale. Nothing redundant and nothing buried.

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 three-optional-parameter tool with no output schema and no annotations, the description covers the core semantics but leaves the return value and the timeout failure mode undefined, which matters for an agent deciding how to handle an unstable screen.

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%, with settle_ms, timeout_ms, and interval_ms each documented including defaults, so the schema does the work. The description adds no parameter guidance beyond implying a poll-and-compare loop; 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?

States a specific action and a precise condition: wait until two consecutive simulator captures are identical. The mechanism (consecutive-capture comparison) makes it clearly distinct from capture/screenshot siblings, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The clause 'so screenshots and assertions are not taken mid-animation' tells the agent exactly when to call it: before get_screenshot, capture_window, or assertion checks. It gives no exclusions or guidance on when skipping the wait is acceptable, so it stops short of a 5.

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