Skip to main content
Glama

ie_wait_element

Waits for a page element to appear or disappear before interacting with slow-rendering content, preventing failed actions on not-yet-ready UI.

Instructions

Wait for an element (by/value) to appear — or, with gone=true, to disappear. Use before acting on slow-rendering content.

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": {
      "by": "<by>",
      "value": "<value>"
    },
    "name": "ie_wait_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
goneNowait for it to disappear instead
frameNo
valueYes
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 20)
intervalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the two modes and the slow-rendering context, but says nothing about what happens when the wait times out (error, false return, no output schema exists), whether it polls, or whether a driver/session must be attached.

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?

Two compact sentences, front-loaded with the action and the mode switch, with no filler. It is arguably too sparse rather than bloated, but nothing is wasted.

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 a 7-parameter wait tool with no annotations, no output schema and low schema coverage, the description is far too thin. It does not explain failure/timeout behavior, the return value, or the frame/interval parameters that an agent must nevertheless set or rely on.

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 43%, so the description should compensate, but it only names 'by/value' without explaining what locator kinds 'by' accepts. The gone, target and timeout semantics live in the schema; frame and interval are undocumented in both places.

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 verb+resource ('Wait for an element') and adds the two meaningful modes: appear by default, disappear with gone=true. It does not, however, distinguish itself from the clearly related siblings ie_wait_ready and ie_wait_text, which an agent must choose among.

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

Usage Guidelines3/5

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

'Use before acting on slow-rendering content' gives a clear trigger condition, but there is no guidance on when to prefer this over ie_wait_ready or ie_wait_text, nor any exclusion such as waiting for a page load versus a specific element.

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