Skip to main content
Glama

SIP call detail

sip_call_detail
Read-onlyIdempotent

Retrieve one SIP call by Call-ID from a capture to analyze its INVITE dialog: message ladder, outcome, setup timing, retransmissions, Reason/Warning headers, and SDP media negotiation.

Instructions

Everything about one SIP call (INVITE dialog) by Call-ID: the message ladder (messages carrying SDP are marked), From/To/Request-URI/P-Asserted-Identity, the outcome (answered, failed , cancelled, no final response), final_response with its reason phrase, timing: post-dial delay (INVITE to the first 180/183, or to the failure response when there was none, as RFC 6076 defines Session Request Delay), ringing, answer and setup (ACK) times, early media (SDP in a 18x) and the call duration from 200 OK to BYE; retransmissions per message; every Reason header with its Q.850 cause named and every Warning header; who ended the call (ended_by: BYE or CANCEL from the caller or callee side, told apart by the From tag); and media: each SDP with its offer/answer role, address, port, codecs, direction and ptime, the codecs offer and answer share and the negotiated one. For the RTP itself use rtp_streams with the same call_id.

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": {
      "path": "<path>",
      "call_id": "<call_id>"
    },
    "name": "sip_call_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoSame forms as start
pathYesCapture file (absolute, in an allowed dir) or open_capture handle
startNoISO 8601, epoch s, +Ns from start, -Ns from end
redactNoReplace subscriber identifiers in this result with tokens; ids+ips hides every IP toooff
call_idYesSIP Call-ID of the call
esp_nullNoRead SIP in NULL-encrypted ESP

Output Schema

NameRequiredDescriptionDefault
callNokeys: call_id, time, duration_ms, src, dst, initial_method, request_uri, from, to, p_asserted_identity, final_status, time_to_final_ms, outcome_status, attempts, resent_messages, no_final_response, message_count, methods, messages, outcome, caller, final_response, provisional, timing, retransmissions, reasons, warnings, ended_by, media
errorNo
foundNo
ipsecNokeys: esp_packets, spis, decoded_null, unreadable, esp_null, hint
windowNo
packets_scannedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, non-destructive read, so the safety profile is covered elsewhere. The description adds real semantics beyond that: how post-dial delay is computed per RFC 6076, how duration is bounded (200 OK to BYE), how outcome is classified, and how ended_by is derived from the From tag. Much of the field enumeration overlaps the output schema, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded correctly, but the body is a single semicolon-chained sentence of a dozen clauses that is dense and hard to scan. Information density is high with little filler, yet grouping the timing, outcome, and media items into discrete sentences would make it far more usable.

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

Completeness5/5

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

For a complex analysis tool with an output schema and full annotation coverage, nothing an agent needs in order to call it correctly is missing: the key, the scoping, the failure/answer outcomes, and the sibling hand-off for RTP are all present.

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 100%, so the baseline is 3. The description only reinforces that call_id is the SIP Call-ID and implies path is a capture; it adds no guidance on redact, esp_null, or the start/end windowing forms beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('one SIP call (INVITE dialog)') and the exact key that selects it (Call-ID), then enumerates what is returned. That is enough for an agent to distinguish it from list-style siblings such as sip_dialogs or packet_detail without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule for the adjacent need: 'For the RTP itself use rtp_streams with the same call_id.' It does not, however, state when to prefer this over sip_dialogs or packet_detail, so the exclusion boundary is partial rather than fully drawn.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.