Skip to main content
Glama

glass_wait_stable

Read-only

Wait for the UI to settle until consecutive frames stop changing, then return the final stable frame. Use a stability region to focus on specific content and ignore moving elements.

Instructions

Wait for visual quiescence: consecutive frames stop changing, then return the last frame. This proves stability, not that an expected semantic state or pixel design was reached; use glass_wait_for_element for a semantic condition/value or glass_wait_for_region with a baseline for expected pixels. Optional stability_region watches only that sub-rectangle; optional region crops the returned frame. Set include_image:false for text-only metadata. If at least two next actions or waits are known, use glass_do instead of separate calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ignoreNoWindow-relative rectangles to exclude from the settle comparison. Use for perpetually animating content — a blinking text caret, a clock, a spinner — which otherwise keeps the window from ever settling. Pixels inside a rect never count as changed and never set `saw_motion`. Combines with `stability_region`: rects are always window-relative and are intersected with it. Independent of `region`, which only crops the returned image. A rect that falls partially or entirely outside the compared area — the frame, or the `stability_region` sub-rectangle when one is set — is silently clamped or dropped, masking less than requested or nothing at all; the excluded count is reported as `ignored_pixels`, so a smaller-than-expected value flags a misplaced rect.
regionNoOptional window-relative sub-rectangle for the returned frame.
toleranceNoPer-channel difference (0–255) two frames may have and still count as unchanged (default 0, exact match). Raise it for a backend with dithering or compression noise.
window_idNoCapture/observe this window (id from `glass_list_windows`) instead of the active one, without changing which window subsequent ops target. Omit for the active window.
timeout_msNoGive up after this long (default 5000ms); returns `{settled:false}` rather than erroring.
interval_msNoHow long to wait between capture ticks (default 100ms).
include_imageNoReturn the settled frame as an image (default true). Set false for a text-only `{settled, saw_motion, observed_ms, ignored_pixels, width, height}` result with no WebP — cheap when the next step is a text `glass_diff`. `region` is ignored when false.
settle_framesNoConsecutive unchanged frames required before the UI counts as settled (default 3). Raise it for an app that pauses mid-animation.
stability_regionNoOptional window-relative sub-rectangle to watch for settling; when set, the settle decision ignores changes outside it. Independent of `region`.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

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

The description goes beyond the readOnlyHint annotation by clarifying that this tool proves stability, not that a specific semantic state or pixel design was reached — a key behavioral caveat. It also documents the optional include_image:false path for text-only metadata and notes that region only crops the returned frame. It doesn't mention all parameter interactions, but the schema already covers those details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: the core definition and the semantic distinction from sibling tools appear in the first two sentences. The later sentences about optional parameters and batching are efficient. It earns a 4 rather than 5 because it packs several ideas into a dense paragraph and could be slightly more scannable, but it has no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 9 parameters, all documented in the schema, and a readOnlyHint annotation, the description is complete enough. It communicates the tool's guarantee (stability, not semantic state), routes to alternatives, and surfaces the include_image optimization for text-only workflows. An agent can select and invoke this tool correctly without further clarification.

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 parameters thoroughly, including tolerance, stability_region, ignore, window_id, timeout, interval, settle_frames, and include_image. The description adds high-level meaning for stability_region and region and mentions include_image's performance benefit, but the detailed semantics live in the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Wait for visual quiescence' and defines the stopping condition as consecutive frames no longer changing, then returning the last frame. The description also clearly distinguishes this from sibling tools glass_wait_for_element and glass_wait_for_region, so an agent can tell them apart without inspecting schemas.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance by naming alternatives: use glass_wait_for_element for semantic conditions/values and glass_wait_for_region with a baseline for expected pixels. It also gives a batching direction: use glass_do instead of separate calls when at least two next actions or waits are known.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fixed-width/glass'

If you have feedback or need assistance with the MCP directory API, please join our Discord server