Skip to main content
Glama

wait_for_flows

Read-only

Wait for new or updated matching HTTP/HTTPS flows after a cursor, using optional timeout and filters to monitor captured traffic and advance pagination safely.

Instructions

Wait for new or updated matching flows after required after_cursor. timeout_ms 0..30000 (default immediate). Optional observation_id and search filters. Returns on matching flows, timeout, cursor reset or cancellation. Follow pagination before advancing cursor.

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": {
      "after_cursor": "<after_cursor>"
    },
    "name": "wait_for_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
pathNo
limitNo
methodNo
statusNo
timeout_msNo
after_cursorYes
before_cursorNo
observation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, non-idempotent, closed-world. The description adds substantial behavior beyond them: the four return conditions (matching flows, timeout, cursor reset, cancellation) and the 'default immediate' behavior when timeout_ms is omitted. What is missing is what an agent should do on cursor reset or cancellation.

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?

Front-loaded with the core action and the required precondition, then the timeout, then the return conditions. Very tight, though the compressed phrasing of the return conditions borders on cryptic rather than concise.

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

Completeness3/5

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

Nine parameters, no output schema, and no parameter descriptions leave a lot of burden on this short text. It covers the caller's obligations adequately but omits what the returned flows/cursor look like and what to do after a cursor reset or cancellation, which matters for a blocking tool.

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?

Schema description coverage is 0% across 9 parameters, so the description must carry the load. It documents after_cursor as required, gives timeout_ms a 0..30000 bound and default, and names observation_id, but lumps host/path/method/status/limit/before_cursor into an unelaborated 'search filters' phrase, leaving six parameters without semantic meaning.

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?

Uses a specific verb ('wait for') and resource ('flows') and constrains scope to 'new or updated matching flows after required after_cursor'. This distinguishes it functionally from the polling/lookup siblings, though it never names search_flows as the non-blocking alternative.

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

Usage Guidelines3/5

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

The word 'Wait' plus the timeout_ms guidance implies a long-poll/Tail-style usage, and 'Follow pagination before advancing cursor' is a real operational rule. But there is no explicit when-to-use-this-vs-search_flows statement and no when-not guidance.

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