SharkMCP

Overview Schema Source Related Servers Discussions Admin

voip_calls

Detect and list VoIP calls from packet captures, providing state, duration, and participant addresses. Reconstruct call flows from SIP, H.323, MGCP, and SKINNY signalling.

Instructions

VoIP call list with state, duration, and participant addresses.

Detects SIP, H.323, MGCP, and SKINNY calls in the capture and reconstructs the call flow from signalling messages.

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": {
      "alias": "<alias>"
    },
    "name": "voip_calls"
  }
}

Input Schema

Name	Required	Description	Default
`alias`	Yes
`display_filter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 27, 2026

TDQS

C2.7/5.0

Behavior3/5

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

No annotations provided, so description must carry the burden. It discloses that it detects various protocols and reconstructs call flow, but doesn't mention side effects (likely read-only) or output format. Adequate but not comprehensive.

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, front-loaded with key output fields. Concise, though the second sentence is slightly technical. No wasted words.

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

Completeness2/5

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

With no output schema and no annotations, the description should provide more context about return values and prerequisites. It fails to explain parameters or what the output looks like, making it incomplete for a 2-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 2 parameters (alias required, display_filter optional) with 0% description coverage. The description does not explain either parameter, leaving the agent with no semantic guidance beyond the schema.

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 clearly states the tool lists VoIP calls with state, duration, and participant addresses, and mentions specific protocols (SIP, H.323, MGCP, SKINNY) and call flow reconstruction. However, it does not differentiate it from sibling tools like rtp_streams or endpoints.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. It implies it's for VoIP analysis but doesn't specify scenarios or exclusions.

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