Skip to main content
Glama

net-web-media

media_container_inspect

Inspect MP4/ISO-BMFF box atoms (ftyp, moov, mdat, trak), WebM/MKV EBML headers, WAV RIFF chunks, or MP3 ID3/frame headers.

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

Input Schema

NameRequiredDescriptionDefault
filePathNo
base64DataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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, and it adds almost nothing beyond the parsing scope. It does not state that the operation is read-only (only implied by 'Inspect'), what the output looks like, whether large media blobs are size-limited, or how errors (corrupt/unsupported containers) are surfaced.

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?

A single front-loaded sentence with zero filler; the format/atom enumeration is dense but each element contributes to the parsing scope.

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 annotations, no output schema, and 0% parameter coverage, the description should carry much more: input selection semantics, read-only nature, and what the inspection yields. Only the parsing scope is covered, leaving the calling contract largely undocumented for a two-input tool.

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?

Both parameters (filePath, base64Data) are at 0% schema description coverage, and the description never references either one. It does not explain the filePath-vs-base64Data trade-off, precedence when both are supplied, or that neither is required — all of which an agent must know to invoke this correctly.

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 ('Inspect') and resource ('media container') and enumerates the concrete structures it parses (ftyp, moov, mdat, trak boxes; EBML headers; RIFF chunks; ID3/frame headers). An agent knows exactly what this tool does. It does not explicitly distinguish itself from siblings, but the sibling set covers entirely different formats, so ambiguity is low.

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?

Usage is only implied by the format enumeration — an agent can infer 'use this when you have an MP4/WebM/WAV/MP3 file to decode.' There is no explicit when-to-use statement, no prerequisites, no note on when not to use it, and no mention of alternatives. Adequate but with clear gaps.

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