Skip to main content
Glama
Sign In
FilmCraft MCP

FilmCraft MCP

by glorybnat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fc_inspect

Inspect an open FilmCraft project, active sequence, or both to retrieve its bin tree, sequences, tracks, and clips as JSON.

Instructions

Inspect the open filmCraft project and/or active sequence. Returns bin tree, sequences, tracks, and clips as JSON.

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

Input Schema

NameRequiredDescriptionDefault
scopeNoWhat to inspect (default: both).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.24.1

TDQS

A3.6/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. 'Inspect ... Returns ... as JSON' conveys that this is a non-mutating read and enumerates the returned payload (bin tree, sequences, tracks, clips), which is real behavioral value. It omits error behavior when nothing is open, whether the output can be large, and any freshness/caching characteristics.

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?

Two short sentences, zero filler, with the resource scope stated first and the return payload second. Every clause carries information an agent would otherwise have to guess.

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-optional-parameter read tool with no output schema, naming the four returned data categories largely compensates for the absent output schema, and 'open project' hints at the precondition. The remaining gap is failure-mode behavior when no project or sequence is loaded, which is a modest omission given the tool's simplicity.

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% and the single enum parameter is already documented in the schema with its default, so the baseline is 3. The phrase 'and/or' loosely mirrors the 'both' value but adds no syntax or edge-case meaning (e.g., what 'sequence' returns when no sequence is active).

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?

Specific verb (Inspect) plus a specific resource (the open filmCraft project and/or active sequence), with the returned artifact named. It does not explicitly distinguish itself from siblings like fc_describe or fc_exec, so an agent must infer that this is the state-reading tool rather than a command-execution one.

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: 'Inspect the open ... project' suggests reading current state, and the schema's scope enum implies the project-vs-sequence choice. There is no explicit when-to-use, no mention of alternatives such as fc_describe, and no stated prerequisites (e.g., that a project must already be open).

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