Skip to main content
Glama

ie_network_clear

Clears all captured network requests from IE network monitoring so stored traffic is removed while request IDs keep counting.

Instructions

Forget every captured request ie_network holds (ids keep counting).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ie_network_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add one genuinely useful behavioral fact — that internal ids keep counting after the clear, so subsequent entries won't restart at 1 — which an agent could not infer from the empty schema. However, it says nothing about whether capture must be enabled, what is returned, or irreversibility beyond the data loss already implied by "forget every".

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?

A single front-loaded sentence with the key side effect compressed into a parenthetical. Every clause earns its place and nothing is padded.

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

Completeness4/5

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

For the simplest possible tool — no params, no output schema, no annotations — the description covers what is destroyed and the id-counter caveat. Minor gaps remain (return value, interaction with an inactive recorder), but nothing essential to calling it correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. Nothing in the text misdescribes the callable surface.

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?

"Forget every captured request ie_network holds" gives a specific verb (forget/clear) and an explicitly scoped resource (the buffer behind the sibling ie_network). An agent can distinguish this from ie_network itself, which reads the data. It stops short of naming ie_network as the read counterpart in usage terms, hence 4 rather than 5.

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?

Usage is only implied: an agent can infer you call this to reset the network log before a fresh capture, but the description never states that, nor any when-not condition. No alternative (e.g., ie_network to read first) is named. Adequate but with a clear gap.

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