Skip to main content
Glama

probe_media

Inspect a media file to retrieve its duration, resolution, frame rate, and audio/video presence for informed editing decisions.

Instructions

Get duration, resolution, frame rate and audio/video presence of a media file.

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
pathYesAbsolute path to a media file

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of the result (the four probed attributes), which is genuinely useful with no output schema, but says nothing about behavior on missing/corrupt/non-media files, permission needs, or cost of probing large files.

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?

One sentence, zero filler, and the returned attributes are front-loaded so an agent can decide relevance immediately.

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?

For a one-parameter read-only inspection tool, the description covers purpose and the set of returned fields, which is the main gap left by the absent output schema. Only failure-mode behavior is missing.

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?

The single 'path' parameter is fully documented in the schema as an absolute path, so the schema already does the work. The description adds no constraints such as whether remote/relative paths or non-existent files are accepted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') applied to a specific resource ('a media file') and enumerates exactly what is returned: duration, resolution, frame rate, audio/video presence. That distinguishes it cleanly from siblings like get_timeline (edit structure) or transcribe (content extraction).

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: the read-only 'probe' semantics suggest inspecting a file before import/planning, but the description never says when to prefer this over siblings such as get_timeline or import_media, and gives no prerequisites or exclusions.

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