Skip to main content
Glama
Sign In
Scout

Scout

by Lautrek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_wait

Wait for page conditions like navigation, network idle, selector visibility, or timeout to ensure the page is ready before proceeding.

Instructions

Wait for a page condition.

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": {
      "condition": "<condition>"
    },
    "name": "scout_wait"
  }
}

Input Schema

NameRequiredDescriptionDefault
conditionYesWhat to wait for
valueNoSelector string or timeout in ms
timeoutNoMaximum wait time in ms (default: 30000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details such as blocking behavior, effect on page state, or any side effects. It does not disclose that wait blocks until condition is met or timeout, which is critical for an AI agent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence), but it provides only the bare minimum. It's not verbose, but it lacks structure and fails to front-load key details like parameter dependencies or return behavior.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return value, blocking nature, or interactions with other tools. The agent would need to infer too much from the schema alone.

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?

The input schema covers all three parameters with descriptions, so the schema carries the burden. The description adds no extra meaning beyond what the schema provides, resulting in a baseline score of 3.

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 'Wait for a page condition' clearly identifies the action (wait) and resource (page condition), distinguishing it from other page manipulation tools like click or navigate. However, it's somewhat vague and doesn't specify the types of conditions beyond the schema.

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 scout_navigate or scout_click. There is no mention of 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