Skip to main content
Glama
Sign In
mcp-stealth-chrome

mcp-stealth-chrome

by RobithYusuf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wait_for_url

Pause execution until the current browser URL matches a specified regex pattern, with an optional timeout to prevent indefinite waiting.

Instructions

Wait until URL matches a regex pattern.

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": {
      "pattern": "<pattern>"
    },
    "name": "wait_for_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYes
timeoutNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states basic behavior. It does not disclose timeout behavior, whether polling occurs, or what happens on failure (e.g., error vs. return value). Key details like matching scope (current page URL) are implied but not explicit.

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?

The description is a single concise sentence, no wasted words. However, it could be slightly expanded to cover key details without becoming verbose.

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 tool with no annotations, 2 parameters, and an output schema, the description is incomplete. It fails to explain the return value, error handling, or provide context for the sibling tools it competes with.

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%, so the description must explain parameters. It only mentions 'URL matches a regex pattern' but does not describe the 'pattern' format or the 'timeout' unit/behavior. Parameter names are somewhat self-explanatory, but the description adds no additional meaning.

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?

The description clearly states the tool waits for a URL to match a regex pattern, which is a specific action on a specific resource. It distinguishes from sibling tools like 'assert_url_matches' (assertion) and 'wait_for_navigation' (navigation event), making the purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'wait_for' or 'wait_for_navigation'. The description does not mention prerequisites, typical use cases, or when not to use it.

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