Skip to main content
Glama

PCAP: SIP messages

pcap_sip_messages
Read-only

SIP messages of a finished PCAP analysis, exactly as captured (headers and SDP bodies), in time order. Filter by call_id; paged with cursor/limit.

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

Input Schema

NameRequiredDescriptionDefault
limitNomessages per page (default 50, max 200)
cursorNoindex of the first message (from next_cursor)
job_idYesjob_id returned by pcap_analyze
call_idNoonly this call (default: all calls)

Output Schema

NameRequiredDescriptionDefault
totalYes
messagesYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / job_id / description
      Added value: +"job_id returned by pcap_analyze"
  2. First observed

TDQS

A3.6/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. The description adds genuinely useful context beyond them: output is raw capture content rather than a parsed model, results are time-ordered, and paging is cursor-based with a default of 50 and max of 200. It stops short of describing behavior on an incomplete job or result size, so a 3 is fair.

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

Conciseness5/5

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

Two tight sentences with the resource and ordering constraint stated first and the filtering/paging constraints second. No filler, no redundant restatement of the tool name.

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?

Given an output schema, four fully documented parameters, and coverage from annotations, the definition tells an agent enough to invoke the tool correctly. The one weak spot is that the 'finished analysis' prerequisite is implied rather than stated as a hard requirement.

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 100%, so every parameter already has documentation, and this sets the baseline at 3. The description reinforces the call_id filter and the cursor/limit paging model but adds no syntax or edge-case meaning beyond what the schema states.

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 ('SIP messages of a finished PCAP analysis'), scope ('exactly as captured, headers and SDP bodies'), and ordering ('in time order'). It implicitly distinguishes itself from parsed-content siblings like pcap_get_call, but never names an alternative, so it stops short of a 5.

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 'of a finished PCAP analysis' signals a prerequisite (job must be complete) and the description notes call_id filtering, but there is no explicit when-to-use versus pcap_get_call, pcap_get_stream, or pcap_full_report. Usage is only implied.

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