Skip to main content
Glama

ie_wait_text

Polls page text until a specified substring appears or disappears, scanning all frames for slow async content and returning the matching frame plus a preview.

Instructions

Poll until a specific substring appears in the page text (for slow async content). Scans all frames unless 'frame' is given; returns which frame matched + a preview. For 'is the page loaded?' use ie_wait_ready instead.

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": {
      "contains": "<contains>"
    },
    "name": "ie_wait_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
goneNowait for the substring to DISAPPEAR instead of appear (e.g. a spinner)
frameNo
targetNoWhere to act: omit it for the session's IE driver; hwnd:<n> acts over COM on the window <n> (a modal dialog's hwnd from a NOTICE or ie_windows), tab:<n> on an attached tab. Over COM, DOM access is script, input is synthetic (script events and a timer click, not mouse or keyboard input; keys are posted window messages) and only id, name, tag, class, link_text and (documentMode 8+) css locators work.
timeoutNomax seconds (default 45)
containsYes
intervalNopoll seconds (default 2)
case_insensitiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description still discloses meaningful behavior: frame scanning defaults to all frames unless 'frame' is given, and the return includes which frame matched plus a preview. It omits what happens when the timeout elapses (error vs. falsy return), which is important for a polling primitive.

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?

Three compact sentences with zero waste: purpose first, scope/return second, disambiguation last. Every clause earns its place and the routing hint is easy to find.

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 7-parameter polling tool with no annotations and no output schema, the definition covers purpose, frame scope, and return shape adequately. It leaves failure semantics (timeout expiry, error vs. negative result) and the 'case_insensitive' behavior undocumented, which an agent would want before relying on a 45-second poll.

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

Parameters4/5

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

Schema coverage is 57%, and the description compensates by explaining 'frame' semantics (all frames are scanned when omitted) and clarifying that 'contains' is matched against page text. The 'target' parameter already has a rich schema description, so the remaining gap is 'case_insensitive', which neither field explains.

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: 'Poll until a specific substring appears in the page text', with the qualifier '(for slow async content)' narrowing intent. It also explicitly distinguishes itself from ie_wait_ready, so an agent can select it without opening any 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?

Gives a clear trigger ('slow async content') and an explicit alternative with its condition: "For 'is the page loaded?' use ie_wait_ready instead." It does not address other plausible neighbors such as ie_wait_element or ie_text, so it falls short of full alternative coverage.

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