Skip to main content
Glama

wait_for_network

Block execution until a network request containing a given URL substring finishes, optionally filtered by HTTP method. Returns the request's URL, status, method, or times out.

Instructions

Block until a network request whose URL contains the given substring completes (optionally filtered by HTTP method), up to timeout. url_pattern is required and is a plain substring match against the full URL including query string — not a regex or glob. Returns the matched request's URL/status/method, or times out. To catch a request fired by a click, run the click and this as consecutive steps in one interact_and_test call; after the fact, read get_response_body/get_network_log instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoHTTP method filter (optional, e.g. 'POST', 'GET')
timeoutNoMax wait time in ms (default: 30000)
session_idYesSession ID
url_patternYesRequired. Plain substring of the full request URL incl. query string (e.g. '/api/tasks', 'graphql') — not a regex; anchors ($) and wildcards (.*) never match.
Behavior5/5

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

No annotations provided, but description fully discloses blocking behavior, timeout, return values (URL/status/method), and plain substring matching. Also explains integration with click events.

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?

Two sentences, no wasted words. Front-loaded with core behavior, second sentence adds important context and alternatives.

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?

Given blocking nature, schema coverage, and no output schema, description explains returns and common pitfalls (regex, interaction with click). Complete for an agent.

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?

Schema coverage is 100%, but description adds crucial details: url_pattern examples and regex warning, method filter purpose, timeout default. Exceeds baseline.

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?

Description clearly states the tool blocks until a network request matching a URL substring completes. It distinguishes from sibling tools like get_response_body and get_network_log by noting they are for after-the-fact reading.

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

Usage Guidelines5/5

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

Explicit guidance: use with interact_and_test for click-triggered requests, and use get_response_body/get_network_log for after-the-fact. Clarifies url_pattern is plain substring, not regex.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/segentic-lab/periscope-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server