Skip to main content
Glama

Capture quality

capture_quality
Read-onlyIdempotent

Assess whether a capture supports loss and timing conclusions before treating retransmissions or missing packets as faults; reports drops, duplicates, truncation, and timestamp issues.

Instructions

Can loss and timing conclusions be drawn from this capture? Call it before reading retransmissions or missing packets as network faults. It reports copies of one packet (with the likely cause), capture drops versus network loss, truncated and oversized frames, checksum offload, one-sided flows and timestamp problems, and verdict.loss_conclusions (trustworthy, use with care or not trustworthy) with the reasons. More detail: resource schema://tools/capture_quality.

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

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
lastNo
pathNo
errorNo
firstNo
framesNo
windowNo
verdictNokeys: loss_conclusions, summary, reasons, notes
checksumsNokeys: validated, bad, bad_by_sender, bad_tcp_data_segments, bad_tcp_segments_acknowledged, likely_offload, explanation
one_sidedNokeys: tcp_streams, tcp_one_direction, tcp_one_direction_short, tcp_syn_unanswered, udp_flows, udp_one_way_flows, examples
duplicatesNokeys: copies, share, causes, examples, repeated_identical
duration_sNo
interfacesNo
ip_packetsNo
link_typesNo
timestampsNokeys: backwards_jumps, max_backwards_s, first_backwards_frame, identical_to_previous, identical_share, resolution, largest_gap_s, largest_gap_after_frame, before_year_2000
encapsulationsNo
tcp_capture_gapsNokeys: tcp_data_segments, missed_by_capture, missed_bytes, directions_with_missed, lost_before_capture, retransmitted_after_capture, out_of_order, unresolved_gaps
truncated_framesNokeys: frames, share, snaplen, protocols
oversized_packetsNokeys: packets, max_ip_len, link_mtu

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, non-destructive and closed-world, so safety is covered; the description adds real behavioral context by disclosing the verdict taxonomy (trustworthy / use with care / not trustworthy) and the categories of artifacts it inspects. It does not mention cost, performance, or what happens when the capture is unreadable, so it stops short of a 5.

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 decision question, followed by the ordering guidance, then the report inventory, then a pointer to the resource schema. The report enumeration is long but each item is a distinct finding category; only the trailing 'More detail:' link is mild overhead.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 explained, and the description still supplies the one piece of interpretive context an agent needs: what verdict.loss_conclusions means and how to act on each value. For a read-only diagnostic with full schema coverage, nothing material is missing.

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 path, start, end and redact are already fully documented in the schema. The description adds no parameter-level detail of its own, so the baseline of 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?

The description opens with a specific question the tool answers (can loss and timing conclusions be drawn from this capture) and then enumerates exactly what it reports: duplicate copies with likely cause, capture drops versus network loss, truncated/oversized frames, checksum offload, one-sided flows, timestamp problems, plus a verdict field. This is a distinct verb+resource framing that separates it from capture_metadata, pcap_info or tcp_health.

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?

It gives an explicit precondition: call it before reading retransmissions or missing packets as network faults, which tells the agent exactly when this tool must precede interpretation. It does not name a specific alternative tool or state when to skip it, which keeps it just below a 5.

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