Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_pcap_triage

Analyze offline PCAP/PCAPNG files with fixed tshark arguments and no name resolution to report packet, endpoint, protocol, and DNS/HTTP/TLS observations—without capturing or replaying traffic.

Instructions

Analyze a supplied PCAP/PCAPNG offline with fixed tshark arguments and name resolution disabled. Reports packet, endpoint, protocol and DNS/HTTP/TLS observations; never captures or replays traffic.

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>",
      "path": "<path>"
    },
    "name": "oc_pcap_triage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
max_bytesNo
max_packetsNo
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Adds real context beyond the annotations: fixed tshark arguments (no caller-supplied flags), name resolution disabled (no outbound DNS, deterministic output), and an explicit no-capture/no-replay guarantee. It does not explain that results are presumably recorded against engagement_id even though readOnlyHint=false, nor any truncation behavior on oversized files.

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?

Two sentences, both load-bearing: the first states the operation and its fixed configuration, the second states the outputs and the safety boundary. Nothing is padded or repeated from the schema.

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?

The output schema covers return values, and the safety profile is covered by annotations plus the no-capture clause. However, for an analysis tool that can be pointed at arbitrarily large captures, the absence of any explanation of the size/packet caps and what happens when they are hit leaves a meaningful gap.

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%, so the description carries the full burden for four parameters, yet it explains none of them. Only "path" is indirectly implied by "supplied PCAP/PCAPNG"; max_bytes, max_packets and engagement_id get no meaning, units, or default rationale anywhere.

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?

"Analyze a supplied PCAP/PCAPNG offline" gives a specific verb and resource, and the note that it never captures or replays traffic separates it from live-capture siblings. It stops short of naming a specific sibling to route against, but the scope is unambiguous.

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 implies usage (you already have a capture file, you want passive inspection) and excludes live capture, but it never states when an agent should pick this over oc_file_triage or a dedicated protocol analyzer. The reader must infer the selection rule.

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