Skip to main content
Glama

binary-forensics

pcap_inspect

Parse libpcap (.pcap) packet capture headers and decode Ethernet, IPv4, TCP, UDP, and DNS/HTTP packet summaries.

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": "pcap_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo
maxPacketsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It says what gets parsed and decoded, but does not disclose whether parsing is strictly read-only, how maxPackets truncates output, how large captures are handled, or what the response looks like. For a file-processing tool with no annotations or output schema, this leaves meaningful behavioral gaps.

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 definition is a single front-loaded sentence with no filler, and the core parsing scope is stated first. Every word contributes to the stated purpose.

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?

The tool has three parameters, zero schema descriptions, no annotations, and no output schema, so the description should do more to explain input selection, maxPackets behavior, and output shape. It adequately covers what protocol layers are decoded but not how to invoke the tool correctly across its input modes.

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 needs to explain the three parameters, but it mentions none of them. Parameter names like filePath and base64Data are somewhat self-explanatory, yet the description never clarifies their relationship, mutual exclusivity, or the truncation/performance meaning of maxPackets.

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 a specific verb, 'Parse,' and a specific resource, libpcap (.pcap) packet capture headers, then adds the exact protocol layers decoded: Ethernet, IPv4, TCP, UDP, and DNS/HTTP summaries. That scope is distinct from every listed sibling tool, which inspect other binary formats.

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 when to use it by naming .pcap packet captures, but it never states when not to use it or how it relates to alternatives such as hexdump_inspect or binary_triage. It also gives no guidance on choosing between filePath and base64Data input modes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources