Manos MCP

Overview Schema Source Related Servers Discussions Admin

Clear captured requests

network_clear

Clear captured network requests for a device while keeping the network capture active, useful for isolating new traffic during mobile UI testing.

Instructions

Clear the captured-request buffer without stopping the capture.

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": {
      "device_id": "<device_id>"
    },
    "name": "network_clear"
  }
}

Input Schema

Name	Required	Description	Default
`device_id`	Yes	Device id from list_devices (adb serial like 'emulator-5554', or an iOS simulator UDID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosure. It explicitly states that the buffer is cleared and that capture continues, which are the key behavioral traits. It does not mention data irreversibility, but that is inherent in the word 'clear'.

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?

The description is a single, front-loaded sentence that conveys all necessary information without redundancy. Every word earns its place.

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?

For a tool with one well-documented parameter and no output schema, the description plus schema fully equip an agent to invoke it correctly. The description covers the action and its critical nuance, making the tool self-contained.

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?

The schema already provides 100% coverage for the sole parameter, device_id, with detailed format and source information. The description adds no additional parameter context, which is acceptable given the schema's completeness.

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 uses the specific verb 'Clear' and identifies the resource 'captured-request buffer', and adds the crucial scope condition 'without stopping the capture'. This clearly distinguishes it from sibling tools like network_stop or network_requests.

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?

The phrase 'without stopping the capture' provides clear context for when to use the tool while a capture is ongoing. It does not explicitly name alternatives or exclusions, but the intent is effectively conveyed for a simple utility.

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