Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_browser_network_log

Destructive

Retrieve complete request and response metadata captured by a live browser session, with optional pagination and log clearing for accurate traffic analysis.

Instructions

Return complete request/response metadata captured by a live browser session, optionally clearing the in-memory log afterward.

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

Input Schema

NameRequiredDescriptionDefault
clearNo
limitNo
offsetNo
session_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description corroborates this by naming the in-memory log as what gets destroyed when clearing. It adds useful specificity, but it does not say whether the clear is irreversible, whether the returned payload is captured before or after clearing, or anything about pagination across the default limit of 500.

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 with the resource named first and the optional side effect second; no filler or restatement. It is tight, though also too brief to cover the parameter surface.

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

Completeness2/5

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

An output schema exists, so return-value detail is not required. However, for a non-idempotent call with a destructive flag and four undocumented parameters, the description leaves too much open — notably how limit/offset interact and whether destructive clearing is recoverable.

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

Parameters2/5

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

Schema description coverage is 0% across five parameters, so the description must carry the load, but it only gestures at 'clear'. limit, offset, engagement_id, and session_id receive no explanation of format, default behavior, or paging semantics.

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?

The description gives a specific verb and resource ('Return complete request/response metadata') scoped to 'a live browser session', which is far more informative than the bare tool name. It does not distinguish this from plausibly overlapping siblings such as oc_browser_network_rules or oc_network_mapper, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this versus alternatives, nor any prerequisite beyond the implicit need for an active browser session. The only usage-adjacent hint is 'optionally clearing the in-memory log afterward', which explains the clear parameter rather than tool selection.

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

Deploy Server

Other Tools