Skip to main content
Glama

net-web-media

webrtc_sdp_inspect

Parse WebRTC Session Description Protocol (SDP) offers/answers for media sections (audio/video/application), codecs (VP8/VP9/AV1/Opus), ICE candidates, and DTLS fingerprint.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "webrtc_sdp_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and 'Parse' only weakly implies a read-only, non-mutating operation without saying so. It does not state what the output looks like, whether parsing failures are reported or thrown, or how the two input modes differ in behavior.

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 the verb first and the extracted artifacts enumerated after. No filler or redundancy, though the parenthetical acronym expansion and codec list are somewhat dense.

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?

For a parser with two undocumented, non-required input parameters and no output schema, the description omits the essential mechanics: how raw SDP is supplied and what the parse result contains. It names the domains parsed but not the shape of the response or error behavior.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, and the description never mentions 'text' or 'filePath' at all. Critically, it does not explain that one of the two must be supplied (both are optional per schema), leaving the agent to guess the input contract.

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 verb ('Parse') and a specific resource ('WebRTC Session Description Protocol offers/answers'), then enumerates what is extracted: media sections, codecs, ICE candidates, and DTLS fingerprint. This clearly separates it from generic siblings like media_container_inspect, though it never explicitly names a sibling or contrast case.

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?

There is no when-to-use guidance, no preconditions, and no mention of alternatives or follow-up tools. An agent is told what the tool parses but not in which situations it should reach for it versus other inspection tools.

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