Skip to main content
Glama

Expert info (warnings, malformed packets)

expert_info
Read-onlyIdempotent

Retrieve tshark expert warnings, errors and malformed-packet flags grouped by severity and protocol to catch decode problems before trusting protocol analysis.

Instructions

tshark's own expert information (-z expert): the warnings, errors and malformed-packet flags its dissectors raised while decoding, grouped by severity, group (Malformed, Undecoded, Sequence, Protocol, Checksum, ...), protocol and summary, with the count, the first frame and up to five sample frames of each (an item tshark reports only to its statistics, such as TCP "exceeds MSS", has no frames). severity is the lowest level kept: error, warn (default), note or chat. filter is a display filter that restricts which packets are examined, e.g. diameter or sctp.port == 3868. summary gives counts by severity and protocol and the number of malformed frames. Use it to catch decode problems (a malformed Diameter AVP, an unknown vendor, a GTP IE tshark could not parse) before trusting the protocol tools, and for the TCP sequence problems tshark already flags.

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

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
limitNoMost rows per page
startNoISO 8601, epoch s, +Ns from start, -Ns from end
filterNoExtra display filter, ANDed
offsetNoRows to skip (next_offset)
outputNosummary: all but rows, plus 3 rows (<8 KB)rows
redactNoReplace subscriber identifiers in this result with tokens; ids+ips hides every IP toooff
columnsNoRow keys to keep (frame keys stay)
severityNoLowest severity listed: chat, note, warn, errorwarn
max_output_kbNoLower output cap, KB

Output Schema

NameRequiredDescriptionDefault
countNo
errorNo
itemsNorows with keys: severity, group, protocol, summary, count, first_frame, frames, frame_count
offsetNo
windowNo
droppedNo
summaryNokeys: by_severity, by_protocol, malformed_frames, malformed_first_frames
has_moreNo
returnedNo
severityNo
next_offsetNo
total_foundNo
total_matchedNo
display_filterNo
packets_matchedNo
packets_scannedNo
total_is_lower_boundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive behavior. The description adds genuinely useful traits beyond that: grouping by severity/group/protocol, up to five sample frames, and the quirk that statistics-only items such as TCP 'exceeds MSS' carry no frames. It does not address pagination behavior or output volume limits, so the added context is real but partial.

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 mechanism and result shape, then parameter meanings, then usage. Dense but every clause carries information; the parenthetical about statistics-only items is long but earns its place. Slightly heavy for a single paragraph.

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?

An output schema exists, so return values need not be restated; the description nonetheless characterizes the row and summary shapes. Paging parameters (offset, limit, max_output_kb) and start/end are left to the schema, which documents them, so the remaining gap is minor for an 11-parameter tool.

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 baseline is 3. The description still adds meaning: severity is the lowest level kept (error, warn default, note, chat) with the ordering spelled out, filter is an ANDed display filter with concrete examples (`diameter`, `sctp.port == 3868`), and summary is described as counts plus malformed-frame count.

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?

Names the exact underlying mechanism (tshark -z expert) and the resource: dissector-raised warnings, errors and malformed-packet flags grouped by severity, group, protocol and summary. That level of specificity lets an agent distinguish it from protocol-specific siblings without opening the schema.

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?

States a clear when-to-use: catch decode problems (malformed Diameter AVP, unknown vendor, unparsed GTP IE) before trusting the protocol tools, and for TCP sequence problems. It gives conditions but does not name a concrete sibling alternative or a when-not-to-use case.

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