Skip to main content
Glama

Read a session's network calls

writ_browser_network
Read-onlyIdempotent

Searches (operation=search, query, method) or reads in full (operation=detail, index) the backend requests the page made after capture_network: the site's real API. writ_browser_act api_call probes one with other values (a flow: several requests); an index feeds writ_browser_compose define_function from_index.

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": {
      "session_id": "<session_id>"
    },
    "name": "writ_browser_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNodetail: which call.
queryNoSubstring filter.
methodNoHTTP method filter.
offsetNo
max_charsNo
operationNosearch (default) | detail.
session_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_chars
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed6 schema fields changed
    • changedInput schema / properties / index / description
      Previous value: -"Which call to read, for operation=detail."New value: +"detail: which call."
    • removedInput schema / properties / max_chars
      Removed value: -{
      -  "description": "Window size, 1000-10000 (default 8000; larger values are clamped); offset pages it.",
      -  "type": "integer"
      -}
    • changedInput schema / properties / method / description
      Previous value: -"Filter by HTTP method."New value: +"HTTP method filter."
    • removedInput schema / properties / offset
      Removed value: -{
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedInput schema / properties / operation / description
      Previous value: -"search (default) | detail. list/get are aliases."New value: +"search (default) | detail."
    • changedInput schema / properties / query / description
      Previous value: -"Substring filter across method, url, status, and bodies."New value: +"Substring filter."
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavior: results are scoped to a prior capture_network session and are the site's real API traffic. However, it says nothing about paging (offset), result truncation (max_chars), or what a returned record contains, which are the behaviors an agent most needs here.

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?

A single front-loaded sentence names the two modes before the cross-references, with no filler. The parenthetical asides ('a `flow`: several requests') are compressed to the point of being cryptic, which costs a little clarity.

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?

With 7 parameters, no output schema, and only 57% schema description coverage, the description should carry more weight. It covers the operation split and the capture prerequisite well, but leaves offset, max_chars, and the shape of returned calls unexplained, so an agent still guesses at pagination and result format.

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

Parameters4/5

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

Schema coverage is only 57% and the schema descriptions are terse, so the description's mapping of operation=search to query/method and operation=detail to index adds real meaning beyond the schema. offset and max_chars remain undocumented in both places, keeping this short of a 5.

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 two specific operations (search with query/method, detail with index) over a named resource: the backend requests the page made after capture_network. It explicitly distinguishes itself from writ_browser_act api_call (which probes one call with other values) and points forward to writ_browser_compose define_function, so an agent can place it in the workflow without opening a schema.

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 clear selection context: use this to enumerate or read captured calls, use writ_browser_act api_call to replay/probe one, and use an index as input to define_function. It also states the prerequisite (capture must have run). What it lacks is an explicit when-not-to-use case, e.g. whether this returns live traffic versus a stored session snapshot.

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.