Skip to main content
Glama

Sevana Voice Quality

PCAP: one SIP call

pcap_get_call
Read-only

One SIP call of a finished PCAP analysis: peers, user agents, response codes, timing, the SIP message ladder (method or status line per message), health warnings and the call's streams.

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>",
      "call_id": "<call_id>"
    },
    "name": "pcap_get_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
call_idYesSIP Call-ID, as listed by pcap_summary

Output Schema

NameRequiredDescriptionDefault
healthYesanalyzer warnings: one-way audio, codec/ptime asymmetry, late media, ...; empty = healthy
ladderYesSIP flow; full messages via pcap_sip_messages
peer_aYes
peer_bYes
call_idYes
streamsYes
media_endNo
reinvitesYes
worst_mosNolowest Sevana MOS of the call's streams
stream_idsYes
diagnosticsNo
media_startNo
useragent_aNo
useragent_bNo
activity_endNo
sip_messagesYes
activity_startNo
response_codesYes
media_duration_sYes

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 establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description usefully adds that this reads a finished analysis and lists the returned sections. It does not disclose behavior for edge cases such as an incomplete job, an unknown call_id, or how the non-idempotent hint manifests in a read-only tool.

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 with no filler; the enumeration is dense but every item is a concrete data element. It borders on a long list, yet nothing is redundant or padded.

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?

An output schema exists, so return values need not be spelled out, and the description does so anyway. What remains missing for a two-required-parameter retrieval tool is failure behavior and the precondition that the job be complete — gaps that matter when passing a job_id that is still processing.

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 50%, with only call_id documented as 'SIP Call-ID, as listed by pcap_summary'. The description compensates by tying job_id to 'a finished PCAP analysis', making it clear that job_id identifies the analysis job rather than an arbitrary handle, though it adds no format or validity details for either parameter.

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 concrete resource — 'one SIP call of a finished PCAP analysis' — and enumerates the payload (peers, user agents, response codes, timing, message ladder, warnings, streams), so an agent knows exactly what it gets back. It does not explicitly contrast itself with pcap_summary or pcap_sip_messages, leaving sibling differentiation to the name and title.

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: the call_id parameter note says 'as listed by pcap_summary', which hints at the discovery-then-fetch workflow. There is no explicit statement of when to call this versus pcap_summary, pcap_sip_messages, or pcap_full_report, and no stated prerequisite that the job must be finished beyond the word 'finished' in the first clause.

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