Skip to main content
Glama

One packet in detail

packet_detail
Read-onlyIdempotent

Decode a single frame into its full protocol layer tree with tshark field names, letting you verify a packet row or trace nested fields at a chosen depth.

Instructions

The full dissection of one frame as tshark decodes it: every protocol layer with its fields, nested as in Wireshark's packet details pane, with tshark's names for enumerated values. Use it to check a row from another tool against the packet: rows carry frame numbers (frame, request_frame, answer_frame, first_frame, ...). layers keeps only these protocols, e.g. ["diameter"] or ["ip", "gtpv2"] (the frame layer is always kept). At most max_fields leaf fields are returned (default 300, server cap 2000); when the cap bites, the innermost layers are kept first and fields_dropped counts the rest. Values longer than 512 characters are cut.

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>",
      "frame": "<frame>"
    },
    "name": "packet_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
frameYesFrame number
layersNoProtocol layers to keep, such as ["diameter"]
redactNoReplace subscriber identifiers in this result with tokens; ids+ips hides every IP toooff
max_fieldsNoMost fields returned

Output Schema

NameRequiredDescriptionDefault
pathNo
timeNo
errorNo
frameNo
layersNo
lengthNo
windowNo
malformedNo
protocolsNo
fields_droppedNo
fields_returnedNo
values_shortenedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial semantics they cannot: the `max_fields` server cap of 2000, the innermost-layers-first retention policy when the cap bites, the `fields_dropped` counter, and the 512-character value truncation. These are exactly the behaviors an agent needs to interpret partial results correctly.

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?

Front-loaded with the core purpose, then the usage rationale, then parameter behavior — a logical progression with no filler. It is dense and slightly long, but each clause (cap, ordering, truncation) carries distinct operational 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, the description needn't explain return values, and it still covers layer filtering, field caps, truncation, and the cross-tool frame-number linkage. Minor gaps remain — no mention of behavior for an out-of-range frame or how `redact` interacts with the dissection — but nothing critical for correct invocation 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?

Schema coverage is 100% so the baseline is 3, but the description adds meaning beyond the schema: the `layers` filter keeps the frame layer always, and `max_fields` is described with both its default (300) and a server ceiling (2000) plus the ordering rule that the schema omits. Only the `redact` behavior is left entirely to the schema.

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 and resource — 'the full dissection of one frame as tshark decodes it' — and immediately characterizes the output shape (every protocol layer with its fields, nested like Wireshark's details pane). This is clearly distinguishable from the many aggregate/summary siblings such as conversations or expert_info.

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?

Gives an explicit use case: validate a row from another tool against the packet, noting that rows carry frame numbers (`frame`, `request_frame`, `answer_frame`, `first_frame`). That is real when-to-use guidance tied to the sibling ecosystem, though it never states when NOT to use it (e.g., for scanning many frames, use filter_packets).

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