Skip to main content
Glama
Sign In
Theseus

Theseus

by ywapom
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wait_for

Pauses browser execution up to 8 seconds until quoted text appears, or waits for the page to settle when no quoted text is supplied.

Instructions

Wait up to 8 s for text in quotes to appear (e.g. "'Order placed'"); with no quotes, wait for the page to settle.

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": {
      "description": "<description>"
    },
    "name": "wait_for"
  }
}

Input Schema

NameRequiredDescriptionDefault
descriptionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/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 behavioral burden. It usefully discloses the 8-second timeout and the quote-based condition behavior, but it does not state what happens on timeout or how the wait interacts with page state beyond 'settle'.

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?

The definition is a single front-loaded sentence with no wasted text. It presents the timeout and both invocation modes immediately.

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?

For a simple one-parameter wait tool with an output schema, the description covers the essential invocation behavior and timeout. The main remaining gap is failure/timeout semantics, but return-value details are covered by the output schema.

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 description coverage is 0%, so the description must explain the sole required parameter. It adds meaningful semantics by explaining that quoted content is treated as target text and unquoted input means wait for page settling, though it does not explicitly map this to the parameter named 'description'.

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?

The description states a specific verb and condition: wait up to 8 seconds for quoted text to appear, or wait for the page to settle when no quotes are used. It does not explicitly distinguish this tool from sibling verification or inspection tools such as assert_state.

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?

It gives clear invocation conditions: use quoted text to wait for that text, and omit quotes to wait for page settling. It does not name alternatives or exclusions, so it falls short of full when-to-use/when-not-to-use guidance.

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