Skip to main content
Glama

PCAP: summary

pcap_summary
Read-only

Overview of a finished PCAP analysis: packet totals, SIP calls with their health warnings, and streams ordered worst Sevana MOS first, each with codec, MOS, loss, jitter and impairments.

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": {
      "job_id": "<job_id>"
    },
    "name": "pcap_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesjob_id returned by pcap_analyze
max_callsNocalls to list (default 50, max 200)
max_streamsNostreams to list (default 50, max 200)

Output Schema

NameRequiredDescriptionDefault
callsYes
job_idYes
omittedNocalls/streams left out of the lists; see pcap_full_report
packetsYesmain packet counters
streamsYes
softwareNo
call_listYes
worst_mosNo
average_mosNo
stream_listYesworst Sevana MOS first
streams_scoredYesstreams with a Sevana MOS

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / job_id / description
      Added value: +"job_id returned by pcap_analyze"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral value beyond that: results are ordered worst Sevana MOS first, calls carry health warnings, and streams are enriched with codec/MOS/loss/jitter/impairments. It does not explain why idempotentHint is false or what happens when the job is still running, which is the notable remaining gap.

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?

A single front-loaded sentence that leads with what the tool is before listing contents. Dense but every clause maps to real returned content; no filler or repetition of the title.

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 explained, and the description still summarizes them usefully. With only three fully documented parameters and a read-only annotation, the main thing an agent might still want — behavior when the referenced job is not yet finished — is the only real omission.

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%, with job_id, max_calls and max_streams all documented in the schema including defaults and caps. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific resource (a finished PCAP analysis) and enumerates exactly what the overview contains: packet totals, SIP calls with health warnings, and streams ordered worst-MOS-first with codec, MOS, loss, jitter and impairments. That is enough to distinguish it from pcap_network_stats or pcap_sip_messages by content. It stops short of naming any sibling explicitly, so the differentiation is inferential rather than stated.

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 phrase 'a finished PCAP analysis' implies a precondition (the job must be complete) and implies this is the first-stop overview, but there is no explicit when-to-use versus pcap_full_report, pcap_network_stats or pcap_get_call. Usage is implied by the enumerated content rather than declared.

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