Skip to main content
Glama

Sevana Voice Quality

PCAP: one RTP stream

pcap_get_stream
Read-only

Full detail of one RTP stream: quality (Sevana and network MOS, R-factor, impairments, echo), loss gaps, payload types, DTMF events. include_timeline adds PVQA's per-interval (0.68 s) detector table.

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>",
      "stream_id": "<stream_id>"
    },
    "name": "pcap_get_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
stream_idYes
include_timelineNoadd the per-interval PVQA detector table (large)

Output Schema

NameRequiredDescriptionDefault
streamYesall fields of the stream as reported by the analyzer (no audio)
summaryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this is a safe read (readOnlyHint=true, openWorldHint=false), so the description's main added value is the warning that include_timeline produces a large per-interval table — useful cost guidance. It does not address prerequisites (e.g., whether the job must be analyzed first) or explain why idempotentHint is false for a retrieval operation.

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?

Two sentences with no filler, front-loading the resource and the returned data categories, then the optional timeline flag. The parenthetical metric list is dense but each item carries information.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description does not need to restate return values, so the main gaps are operational: no statement of prerequisites, no guidance on obtaining a valid stream_id, and no explicit differentiation from pcap_get_call or pvqa_timeline. Adequate but with clear omissions for a tool that is the per-stream deep-dive of a larger family.

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 only 33%, and the description adds just one detail beyond the schema: the detector interval is 0.68 s. Neither job_id nor stream_id is clarified (e.g., where a stream_id comes from, or whether it is per-job), leaving the two required parameters undocumented in both places.

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?

Names a specific resource (one RTP stream) and enumerates exactly what detail is returned: quality metrics (Sevana/network MOS, R-factor, impairments, echo), loss gaps, payload types and DTMF events. That is far more specific than the title alone, though it never contrasts itself with siblings like pcap_get_call or pvqa_timeline.

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?

Usage is only implied: an agent can infer it should call this when it needs per-stream detail rather than call-level or report-level views. There is no explicit when-to-use, when-not-to-use, or named alternative, and the include_timeline note only hints that pvqa_timeline may overlap.

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