Skip to main content
Glama

probe_media

Read-only

Inspect a media file to return codec, stream, duration, size, frame rate, and portrait-orientation details so you can plan edits before importing or cutting clips.

Instructions

Media info for a file (codecs, size, rate, duration, streams) as FilmCraft decodes it, with a summary: seconds, size, fps and whether it is portrait.

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": {
      "path": "<path>"
    },
    "name": "probe_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the return contents and noting that values reflect FilmCraft's own decoding rather than an external tool's, but it says nothing about behavior on unsupported/corrupt files or missing paths.

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?

One dense sentence that front-loads the resource and enumerates results without filler. The parenthetical plus trailing summary clause makes the grammar slightly tangled, but every element carries information.

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?

With one required parameter, no output schema, and read-only annotations, the description covers what an agent needs: it says what the tool reads and roughly what it returns. Given there is no output schema, a brief note on failure behavior would be the only remaining gap.

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 0% and the single 'path' parameter is an untyped-in-prose string. The phrase 'media info for a file' implies the parameter is a filesystem path to a media file rather than a project or URL, which is a marginal but genuine clarification beyond the bare 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?

States a specific resource (media metadata for a file) and enumerates exactly what is returned (codecs, size, rate, duration, streams, plus a summary of seconds, size, fps and portrait orientation). It is clearly a read-only probe rather than a mutation, which separates it from import_media or ffmpeg_convert, though it never names those siblings explicitly.

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 explicit when-to-use or when-not-to-use guidance. An agent can infer this is the step before import_media or render, but nothing in the text says so, and no alternative for extracting media info (e.g. ffmpeg_run) is mentioned.

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