Skip to main content
Glama

Read buffered client HTTP requests

lol_cdp_network_tail
Read-onlyIdempotent

Inspect captured HTTP requests from the in-memory buffer, filtering by status, URL, or method to find 4xx/5xx errors and hung calls. Requires active network recording.

Instructions

Retrieve captured HTTP network requests from the in-memory buffer, filtered by status, URL pattern, or HTTP method. Use this tool to inspect recent client network calls and identify 4xx/5xx errors or hung requests. Prerequisite: Must call lol_cdp_network_start first; fails if network recording is not running. To fetch full response bodies, pass returned request IDs to lol_cdp_network_body. For aggregated traffic statistics, use lol_cdp_network_summary instead. Behavior: Returns completed requests and active in-flight requests.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoCDP resource type filter, e.g. "Fetch", "XHR", "Document", or "Script"
limitNoMaximum entries to return (1-2000, default: 100)
sinceNoLower timestamp bound in epoch milliseconds; excludes older requests
untilNoUpper timestamp bound in epoch milliseconds; excludes newer requests
cursorNoSequence cursor from a previous tail call for incremental reading
methodNoHTTP method filter matching verbs case-insensitively, e.g. "GET" or "POST"
statusNoExact HTTP response status code to match, e.g. 404 or 500
targetIdNoFilter requests to a specific CDP renderer target ID
minStatusNoMinimum HTTP status code threshold; pass 400 to find all client and server errors
failedOnlyNoIf true, filters strictly for low-level transport/network failures (excludes HTTP 4xx/5xx)
urlContainsNoCase-insensitive substring filter matching request URLs, e.g. "/lol-champ-select/"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safe-read profile, but the description adds real behavioral context: the precondition that recording must be running, and that returns include both completed and active in-flight requests. This goes beyond what the annotations provide.

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?

Front-loaded with the core action, then purpose, prerequisite, and alternatives in a logical order. Every sentence earns its place with no redundancy.

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?

With no output schema, the description responsibly states what is returned (completed plus in-flight requests), covers the prerequisite that gates successful invocation, and routes to sibling tools for bodies and aggregate stats.

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 coverage is 100%, so all 11 parameters are already documented, including filters like status, urlContains, minStatus, and cursor. The description only restates the filter dimensions (status, URL pattern, method) without adding syntax or semantics beyond the schema, which is the expected 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?

States a specific verb (Retrieve) and resource (captured HTTP network requests from the in-memory buffer) with the filtering scope. It distinguishes itself from siblings by naming lol_cdp_network_body for bodies and lol_cdp_network_summary for stats.

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 when-to-use ('inspect recent client network calls and identify 4xx/5xx errors or hung requests'), a hard prerequisite (must call lol_cdp_network_start first, fails otherwise), and two named alternatives for adjacent needs.

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