Skip to main content
Glama

Sevana Voice Quality

PCAP: DTMF

pcap_dtmf
Read-only

DTMF key presses found in a finished PCAP analysis, with digits and timing: RTP telephone-events (RFC 2833/4733) per stream and SIP INFO (application/dtmf-relay, application/dtmf).

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

Input Schema

NameRequiredDescriptionDefault
job_idYes
call_idNoonly this call
stream_idNoonly this RTP stream (RFC 2833 events)

Output Schema

NameRequiredDescriptionDefault
countYes
digitsYesall keys in time order
eventsYes

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, openWorldHint=false and idempotentHint=false, so the safety profile is known. The description adds real context: it works only against a finished analysis, and results are aggregated per stream across two distinct sources (RTP events vs SIP INFO). It does not disclose volume, truncation, or behavior when only one source has events.

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 with no filler, front-loaded on the resource and followed by the return shape and source protocols. The protocol enumeration is the only heavy part, and it earns its place by telling the agent where the digits come from.

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 details need not be spelled out, and the description covers purpose, sources, and the finished-analysis precondition. The main residual gap is error/empty-result behavior, which is minor for a read-only extractor.

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 coverage is 67% and the schema descriptions already explain call_id ('only this call') and stream_id ('only this RTP stream (RFC 2833 events)'). The description's 'per stream' and the SIP INFO mention add modest framing about scope, but it does not explain job_id or the interaction between call_id and stream_id, so it stays at the baseline.

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?

States a specific resource (DTMF key presses) plus what is returned (digits and timing) and the two detection mechanisms (RTP RFC 2833/4733 telephone-events and SIP INFO dtmf-relay). This clearly separates it from generic SIP or stream tools like pcap_sip_messages and pcap_get_stream, though no sibling is named 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 'found in a finished PCAP analysis' implies the precondition that a completed job is required, which is useful. However, it gives no explicit when-to-use vs when-not guidance, no mention of what happens when a stream carries no DTMF, and no routing to the SIP-message or stream tools for related queries.

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