Skip to main content
Glama
InDate
by InDate

network

Monitor and manage network requests with actions to list, get details, search, enable/disable monitoring, and set throttling conditions.

Instructions

Monitor and manage network requests. Actions: list (list requests with optional type filter and pagination), get (get specific request by ID), search (search requests by regex pattern), enable (enable network monitoring), disable (disable network monitoring), setConditions (set network throttling conditions)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoRequest ID (required for get action)
flagsNoRegex flags (for search action, default: "")
limitNoMax results to return (for list action default: 100, for search action default: 50)
actionYesNetwork action: list (list network requests), get (get specific request details), search (search requests by pattern), enable (enable network monitoring), disable (disable network monitoring), setConditions (set network conditions)
methodNoFilter by HTTP method (for search action)
offsetNoNumber of results to skip (for list action, default: 0)
presetNoNetwork condition preset (required for setConditions action)
patternNoRegex pattern to search for (required for search action)
statusCodeNoFilter by status code (for search action)
includeBodyNoIf true, saves response body to disk and returns file path (for get action, default: false)
resourceTypeNoFilter by resource type (for list and search actions)
connectionReasonNoConnection reference (use the reference from launchChrome output, e.g., "unnamed-connection-default" or your renamed tab)
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects (e.g., enabling/disabling monitoring may be destructive), required permissions, or rate limits. The description only lists actions without behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with a list; it is concise but could be better structured by separating action groups. It front-loads the overall purpose but the list format is somewhat dense.

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?

Given the high parameter count (12), multiple actions, and no output schema, the description covers the basic purpose and actions but lacks details on return values, error conditions, or parameter relationships. It is moderately complete.

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 100%, so the description does not need to compensate. However, the description adds minimal extra meaning beyond the schema, just grouping actions and briefly restating their purposes. A baseline score of 3 is appropriate.

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 the tool purpose as 'Monitor and manage network requests' and enumerates specific actions (list, get, search, enable, disable, setConditions), distinguishing it from sibling tools like 'request' or 'config'.

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 description lists all actions but provides no guidance on when to use this tool versus alternatives or when specific actions are appropriate. The context is implied by action names but no explicit exclusions or prerequisites are given.

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/InDate/cdp-tools-mcp'

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