Skip to main content
Glama

PCAP: full report (paged)

pcap_full_report
Read-only

The complete analysis report, one section at a time: "streams" or "sip_calls" (full objects, paged with cursor/limit) or "counters" (packet counters, SIP statistics, aggregate statistics). Contains no audio.

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>",
      "section": "<section>"
    },
    "name": "pcap_full_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoitems per page: streams default 5 (max 20), sip_calls default 3 (max 10); calls carry all their SIP messages
cursorNoindex of the first item (from next_cursor)
job_idYesjob_id returned by pcap_analyze
sectionYesstreams, sip_calls or counters

Output Schema

NameRequiredDescriptionDefault
totalNo
sectionYes
streamsNo
softwareNo
sip_callsNo
statisticsNo
next_cursorNo
sip_statisticsNo
packet_countersNo
subnet_statisticsNo

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.6/5.0
Behavior3/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 without the description. The description does add real behavioral context beyond them — that streams and sip_calls are returned as full objects paged via cursor/limit, what counters contains, and that no audio is included — but it says nothing about response size, termination behavior, or cost of large pages.

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 dense sentence that front-loads the core idea ('complete analysis report, one section at a time') and then enumerates sections; nothing is redundant. The nested quoting makes it slightly harder to parse on first read, but no sentence is wasted.

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, return-value detail is not required, and all four parameters are documented. The description covers the section semantics and paging model sufficiently for a read-only reporting tool; only minor gaps like page-size defaults and any job-state prerequisites remain.

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, and the description earns the bump by explaining what each section value actually yields (full objects vs packet counters, SIP statistics, aggregate statistics) and tying cursor/limit to the paged access pattern. It still relies on the schema for defaults and maxima.

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 names a specific verb and resource ('the complete analysis report, one section at a time') and enumerates the three section values, so an agent knows exactly what comes back. It does not name any sibling (e.g. pcap_summary, pcap_get_stream) as the narrower alternative, so differentiation is only partial.

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?

'One section at a time' plus the per-section descriptions imply when to reach for this instead of a single-stream or single-call fetch, and 'Contains no audio' quietly routes audio needs elsewhere. However, no explicit when-to-use/when-not-to-use statement or named alternative is given, leaving the agent to infer it from sibling names.

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