Skip to main content
Glama

wait_for_window

Wait for a window with a specific title to appear or disappear, then automatically activate it for further actions. Use after opening or closing windows to ensure the next inputs target the correct window.

Instructions

Wait for a window to appear or disappear.

Polls the window list until a window with a matching title is
found (or gone).  Use after actions that open or close windows.
When found, auto-activates the window so subsequent type_text
and press_key target it.

Args:
    title: Window title to search for (substring match).
    app: Only look for windows in this application.
    timeout: Maximum seconds to wait (default 10).
    gone: If true, wait for the window to DISAPPEAR instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
appNo
timeoutNo
goneNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses polling behavior, auto-activation, and side effects on subsequent type_text/press_key. It lacks details on timeout failure behavior (e.g., exception), but covers major traits.

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?

Description is concise, front-loaded with purpose, and every sentence adds value. Structured with clear paragraphs for parameters.

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?

Given the tool's complexity and absence of annotations, the description covers usage, parameters, and behavior well. Minor gap: no mention of timeout failure behavior, but output schema may cover return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description fully explains all four parameters: title (substring match), app (filter), timeout (max seconds, default 10), gone (wait for disappear). Adds essential meaning beyond schema.

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?

The description clearly states the tool waits for a window to appear or disappear, with a specific verb and resource. It distinguishes from sibling tools like wait_for (generic), wait_for_app (app-specific), and activate_window (no waiting).

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 description explicitly says 'Use after actions that open or close windows,' providing clear context. However, it does not mention when not to use it or list alternatives, though the context is sufficient for most cases.

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

Install Server

Other Tools

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/Touchpoint-Labs/Touchpoint'

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