Skip to main content
Glama

dev_wait

Waits for a CSS-selected element to appear or, with gone set, to disappear before continuing, so UI checks and panel-closure verification are reliable.

Instructions

Wait for an element to appear, or with gone for it to leave the page. The second half is not optional: verifying that a panel closed is impossible without it.

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": {
      "selector": "<selector>"
    },
    "name": "dev_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
goneNoWait for it to disappear instead of appear.
selectorYesCSS selector.
timeout_secondsNoHow long to wait. Default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the two wait conditions and implicitly that the call blocks, but says nothing about what happens on timeout (error, false return, silent pass) — a material gap for a wait primitive.

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 short sentences, front-loaded with the main behavior and no redundant padding. The second sentence is motivational rather than informational, but it is brief and reinforces the `gone` mode.

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 three-parameter tool with full schema coverage and no output schema, the essentials are present. Still missing are timeout failure semantics and what the call yields on success, which an agent needs to handle this tool correctly.

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 coverage is 100%, so all three parameters are already documented, including the `gone` flag. The description only restates `gone` semantics and adds a use-case gloss; no extra syntax, units beyond the schema, or edge-case parameter behavior.

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 covers both modes (appear / leave with `gone`). An agent knows exactly what the tool does, though it does not name or contrast any sibling tool.

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?

Provides a concrete use case for the `gone` mode ('verifying that a panel closed'), which is genuine when-to-use guidance. However, it never states when to reach for this versus other dev_* tools (e.g. snapshot/poll) or when waiting is unnecessary.

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

Deploy Server

Other Tools