Skip to main content
Glama

Capture summary

pcap_info
Read-onlyIdempotent

Summarize a capture file to get packet count, duration, timestamps, size, link type, and top protocol-hierarchy entries before choosing a protocol-specific analysis tool.

Instructions

Summarise a capture file: packet count, duration, first/last timestamp, size, link type and the top protocol-hierarchy entries. Call this first to learn what a capture contains before choosing a protocol tool. path must be inside an allowed directory.

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

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
startNoISO 8601, epoch s, +Ns from start, -Ns from end
redactNoReplace subscriber identifiers in this result with tokens; ids+ips hides every IP toooff

Output Schema

NameRequiredDescriptionDefault
pathNo
errorNo
ipsecNokeys: esp_packets, spis, decoded_null, unreadable, esp_null, hint
limitsNo
windowNo
packetsNo
capinfosNo
file_typeNo
link_typeNo
duration_sNo
last_packetNo
window_hintNo
first_packetNo
file_size_bytesNo
interface_dropsNo
frames_in_windowNo
last_packet_epochNo
first_packet_epochNo
metadata_availableNo
protocol_hierarchyNorows with keys: protocol, frames, bytes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. Beyond that, the description adds a workflow rule (this is the entry-point call) and a filesystem access constraint (path must be inside an allowed directory), which is the kind of prerequisite an agent needs before invoking.

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?

Three sentences, front-loaded with the returned fields, then the sequencing advice, then the path constraint. Nothing is padded and every clause carries information.

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?

With an output schema present and full parameter coverage, the description need not describe return values or argument syntax, and the annotations cover safety. The only residual gap is that it does not clarify how the start/end window interacts with the reported total-duration and packet-count figures.

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?

Schema description coverage is 100%, so start/end forms, the redact enum, and the allowed-directory requirement are all documented in the schema itself. The description adds no extra meaning about start/end windowing or how redaction affects the summary, so baseline 3 applies.

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?

States a specific verb (summarise) and resource (a capture file), then enumerates exactly what comes back: packet count, duration, first/last timestamp, size, link type, top protocol-hierarchy entries. This clearly separates it from the per-protocol siblings like sip_call_detail or tcp_connections.

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?

"Call this first to learn what a capture contains before choosing a protocol tool" gives explicit ordering guidance and a decision rule for this tool versus the protocol tools. It stops short of naming exclusions or contrasting with adjacent summary siblings such as capture_metadata or capture_quality, but the sequencing advice is actionable.

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