Skip to main content
Glama

net-web-media

websocket_frame_decode

Decode raw RFC-6455 WebSocket binary frames (FIN bit, opcode, mask flag, 7/16/64-bit payload length, unmasking XOR key, and decoded payload).

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": "websocket_frame_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
hexDataNo
base64DataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses what gets extracted from the frame, but says nothing about input requirements (hex vs base64, whether one or both are needed), behavior on malformed or truncated frames, handling of text vs binary opcodes or fragmented frames, or what errors look like. For a no-annotation tool this leaves significant behavioral gaps.

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 sentence with the resource front-loaded and the decoded fields grouped in a parenthetical, so there is no filler. The enumerated field list is dense but every item conveys real information about the output. Slightly list-heavy, but nothing is wasted.

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

Completeness3/5

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

For a simple two-parameter decoder with no output schema, the description does the important work of describing the return content, which is otherwise undocumented. However, it omits the input-format choice between hex and base64 and any edge-case behavior, leaving the agent to guess how to actually invoke it.

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% and the description never mentions hexData or base64Data. The agent is not told that the input may be supplied as either hex or base64, whether the two are mutually exclusive, or why neither is marked required. The description must compensate for the empty schema here and does not.

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 names a specific verb ("Decode") and a precise resource ("raw RFC-6455 WebSocket binary frames"), then enumerates the decoded fields: FIN bit, opcode, mask flag, payload length, XOR key, and payload. This is far more specific than a generic "decode" tool and an agent can tell what it produces. It does not explicitly contrast with any sibling such as webrtc_sdp_inspect, which keeps it at 4 rather than 5.

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 prerequisites, and no mention of alternatives or exclusions. The word "raw" weakly implies the input must be a single frame rather than a capture or stream, but the agent must infer that. Nothing tells the agent when this tool is the wrong choice.

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