Skip to main content
Glama
Sign In
FilmCraft MCP

FilmCraft MCP

by glorybnat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc_probe

Retrieve codec, resolution, frame rate, audio tracks, and format-specific metadata for a media file, with optional support for numbered image sequences.

Instructions

Get detailed media information for a file: codec, resolution, frame rate, audio tracks, and format-specific metadata.

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": {
      "file": "<file>"
    },
    "name": "fc_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute path to the media file to probe.
image_sequenceNoTreat the file as the first frame of a numbered image sequence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.24.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. "Get" implies a read-only probe and it discloses the shape of the returned information, which is genuinely useful. However it says nothing about failure behavior on non-media files, remote/relative paths, or whether the call is expensive on 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?

A single front-loaded sentence with no filler. The field enumeration is dense and directly useful rather than padding.

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 two-parameter probe with no output schema, the definition is adequate: it names the metadata categories. But the return format is left vague ("format-specific metadata") and nothing describes output structure or error cases, so it is minimally sufficient rather than complete.

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 description coverage is 100%, so both `file` and `image_sequence` are already documented in the schema. The description adds nothing about parameter behavior, such as what a numbered image sequence implies for the returned metadata. Baseline 3 applies.

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?

Uses a specific verb ("Get") plus a specific resource ("detailed media information for a file") and enumerates the fields returned: codec, resolution, frame rate, audio tracks, format metadata. An agent knows exactly what it gets. It does not differentiate from the sibling fc_inspect, which is the only shortfall.

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 (e.g., file must exist locally, ffmpeg availability), and no mention of when to prefer fc_inspect or fc_render_frame instead. The only usage signal is the tool name and the implied read-only nature of "Get".

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

Deploy Server

Other Tools