Skip to main content
Glama

Sevana Voice Quality

PCAP: network statistics

pcap_network_stats
Read-only

Network view of a finished PCAP analysis: packet and SIP counters, per-stream loss, jitter, delay and network MOS, and the aggregate statistics (correlations of MOS with network features) when computed.

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_network_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes

Output Schema

NameRequiredDescriptionDefault
streamsYes
statisticsNo
sip_statisticsYes
packet_countersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by flagging that aggregate correlation statistics are only present 'when computed', warning the agent about conditionally absent fields. It does not, however, state what happens when the job_id refers to a job that is not finished, which matters because the tool explicitly targets finished analyses.

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?

One dense sentence, front-loaded with the scope ('network view of a finished PCAP analysis') followed by the metric inventory. Every clause maps to content the agent needs, though the metric list is long enough to read as a run-on rather than a structured enumeration.

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 annotations cover the read-only/closed-world profile. The description covers the metric scope and the conditional aggregate stats, leaving only job-state error behavior unaddressed for an otherwise simple one-parameter tool.

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 0%, so the single job_id parameter is undocumented in structured form and the description never mentions it. The 'finished PCAP analysis' framing still implies that job_id must reference a completed analysis job, which adds modest meaning beyond the bare string type, but format or validity expectations are left unstated.

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 resource view tied to a concrete artifact ('network view of a finished PCAP analysis') and enumerates the exact metrics returned: packet/SIP counters, per-stream loss, jitter, delay, network MOS, and MOS/feature correlations. An agent can tell this returns network-layer metrics rather than SIP messages, DTMF events, or stream payloads, though it does not name a sibling alternative explicitly.

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 'finished PCAP analysis' implies the prerequisite that the job must already be complete, which is genuinely useful selection guidance. However, there is no explicit when-to-use versus pcap_summary, pcap_full_report, or pcap_get_stream, and no statement of when this tool should be skipped in favor of those.

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