Skip to main content
Glama

Wait for a crawl

wait_crawl
Read-onlyIdempotent

Wait up to timeoutMs (default 30000, at most 55000) for a crawl to finish and return its report; at the timeout it returns the report so far, so wait again or read get_crawl_pages.

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": {
      "id": "<id>"
    },
    "name": "wait_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYestaskId from crawl
timeoutMsNo

Output Schema

NameRequiredDescriptionDefault
statusYes
taskIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / timeoutMs / maximum
      Previous value: -120000New value: +55000
  2. Changed1 schema field changed
    • changedInput schema / properties / timeoutMs / maximum
      Previous value: -90000New value: +120000
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, it discloses the default and maximum wait, the bounded nature of the wait, and that timeout still returns a partial report rather than necessarily an error. The advice to wait again also clarifies how incomplete results should be handled.

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?

A single compact sentence front-loads the operation and timeout limits, then explains timeout results and follow-up options. Every clause contributes actionable information without unnecessary repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter waiting tool, the description covers the operation, timing limits, incomplete-result behavior, and recovery path. The output schema can describe the report structure, so further return-value detail is not necessary here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents id as the taskId from crawl, while the description supplies the otherwise undocumented timeoutMs default of 30000 and explains its effect. Although the 55000 maximum repeats the schema constraint, the description adds the important partial-report behavior at that boundary.

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 that the tool waits for a specific crawl to finish and returns its report. Its bounded-wait behavior distinguishes it from immediate retrieval tools such as get_crawl and from the batch-oriented wait_batch.

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 a clear usage context—waiting for crawl completion—and explicit next steps on timeout: call it again or read get_crawl_pages. It does not explicitly explain when to prefer get_crawl for an immediate status check, but the timeout fallback is practical guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.