Skip to main content
Glama
Sign In

mcp.film directory

by film.mcp
OverviewDiscussionsAdmin

Plan a full film MCP stack

plan_film_stack
Read-onlyIdempotent

Get a recommended set of MCP servers covering the whole film pipeline (develop → visualize → shoot → sound → cut → finish → ship). Returns 1-3 picks per stage, ranked by official status and hosting. Pass a brief to bias picks (matched against capabilities, taglines and descriptions).

Input Schema

NameRequiredDescriptionDefault
briefNoOptional: what you're making, e.g. 'a 60s commercial with a consistent character and licensed music'
include_inactiveNoAlso consider servers whose status is dead, archived or deprecated. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_inactive
      Added value: +{
+  "description": "Also consider servers whose status is dead, archived or deprecated. Default false.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral detail beyond that: returns are 1-3 picks per stage, ranked by official status and hosting, and briefs are matched against capabilities, taglines and descriptions. It does not cover rate limits or auth, but those are less central for a read-only recommendation tool.

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?

The description is three tight sentences with no wasted wording. The core purpose and scope are front-loaded, followed by return shape and brief behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a recommendation tool with full schema coverage and no output schema, the description provides enough context about scope, return cardinality, ranking logic and brief matching. An agent can call it correctly without needing additional prose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds real semantic value for the brief parameter by explaining that it is matched against capabilities, taglines and descriptions, which goes beyond the schema example.

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 states a specific verb and resource: get a recommended set of MCP servers covering the full film pipeline. It also specifies the pipeline stages and return cardinality. It does not name or distinguish itself from close siblings like recommend_film_mcps or get_film_recommendation, so it falls short of a 5.

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?

The full-pipeline framing implies when this tool is appropriate, and passing a brief is explained as a way to bias picks. However, there is no explicit when-not guidance and no direct comparison to sibling recommendation tools, leaving the agent to infer the best alternative.

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

All mcp.film directory toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources