Skip to main content
Glama

anchor_wait

Waits for named UI anchors to appear or disappear by polling anchor_probe, returning a timeout verdict; read-only and never resends tasks.

Instructions

Poll anchor_probe until every named anchor is present (until=present, the default) or all are gone (until=absent). Read-only; it never resends a task. Timeout is a verdict (ANCHOR_TIMEOUT), not an exception. Ambiguous counts as visible.

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": {
      "hwnd": "<hwnd>",
      "names": "<names>"
    },
    "name": "anchor_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNo
hwndYes
namesYes
storeNo
untilNopresent
roi_padNo
timeoutNo
intervalNo
thresholdNo
color_themeNo
scale_productNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it declares read-only, that it will never resend a task (idempotency), that a timeout yields a verdict (ANCHOR_TIMEOUT) rather than an exception, and that ambiguous states count as visible. It omits any detail on the return payload shape or how polling frequency/threshold behave, so it falls short of exhaustive.

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?

Four dense sentences, each delivering a distinct fact (mode semantics, safety, failure verdict, ambiguity handling) with no filler. The most decision-relevant information (the polling condition) is front-loaded.

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

Completeness2/5

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

For an 11-parameter tool with 0% schema coverage and no output schema, the description covers behavior but leaves most parameters undefined and gives no indication of the return structure. It is helpful on semantics but materially incomplete for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, so the description must compensate, yet it only explains 'names' and 'until' (including the default). Timeout, interval, threshold, hwnd, store, roi_pad, color_theme, and scale_product are left entirely undocumented in both schema and prose.

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 (poll) targeting a specific sibling resource (anchor_probe) with a precise stopping condition (every named anchor present or all gone). An agent can immediately distinguish this waiting variant from a one-shot anchor_probe call without opening either schema.

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?

Explains the two operational modes via until=present (default) and until=absent, giving clear context for which mode to select. It does not explicitly say 'use anchor_probe instead for a single non-blocking check,' leaving that contrast implied rather than stated.

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