Skip to main content
Glama
Sign In

mcp.film directory

by film.mcp
OverviewDiscussionsAdmin

Recommend MCP servers for a brief

recommend_film_mcps
Read-onlyIdempotent

Given a filmmaking brief, return the closest intent-routed MCP recommendations: one compact pick per primary server (slug, role, why, remote, official, verified) plus compact fallbacks. Use hosted_only=true when the agent cannot spawn local tools; get_film_mcp for full server detail.

Input Schema

NameRequiredDescriptionDefault
briefYesWhat you're trying to make, e.g. 'avatar UGC ad with voiceover' or 'search dailies and cut a trailer'
verbosityNocompact (default): one small object per pick in primary/primary_servers and fallback_servers. full: the complete server objects, as before.
constraintsNoHard constraints applied before relevance. Also inferred from the brief ('locally', 'without uploading', 'confidential', 'offline', 'no budget', 'free', 'no local install'). Picks that violate one are excluded; if nothing survives, unsatisfied_constraints explains why.
hosted_onlyNoOnly return hosted remote primary/fallback servers where possible.
include_inactiveNoAlso consider servers whose status is dead, archived or deprecated. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / constraints
      Added value: +{
+  "description": "Hard constraints applied before relevance. Also inferred from the brief ('locally', 'without uploading', 'confidential', 'offline', 'no budget', 'free', 'no local install'). Picks that violate one are excluded; if nothing survives, unsatisfied_constraints explains why.",
+  "properties": {
+    "free_only": {
+      "description": "Only free or freemium pricing.",
+      "type": "boolean"
+    },
+    "has_shell": {
+      "description": "false means the agent cannot run local processes; implies hosted_only.",
+      "type": "boolean"
+    },
+    "hosted_only": {
+      "description": "Only hosted remote MCP endpoints.",
+      "type": "boolean"
+    },
+    "local_only": {
+      "description": "Only servers with a local install path (stdio or local app).",
+      "type": "boolean"
+    },
+    "no_upload": {
+      "description": "Only local servers with no cloud credential, so media never leaves the machine.",
+      "type": "boolean"
+    },
+    "os": {
+      "description": "macos | windows | linux; excludes listings that say they only run elsewhere.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / include_inactive
      Added value: +{
+  "description": "Also consider servers whose status is dead, archived or deprecated. Default false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / verbosity
      Added value: +{
+  "description": "compact (default): one small object per pick in primary/primary_servers and fallback_servers. full: the complete server objects, as before.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for going further: it discloses that results are one compact pick per primary server with compact fallbacks, and that fallbacks exist as a concept. It doesn't explain pagination, result limits, or what happens when nothing matches, which is the main remaining gap.

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 sentences, front-loaded with the trigger condition and resource, followed by the return shape and the escalation path. No sentence is redundant with the name or title.

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 no output schema, the description does the work of naming the returned fields (slug, role, why, remote, official, verified) plus fallbacks, which is enough to act on. It omits the unsatisfied_constraints failure mode and the inactive/deprecated filtering behavior, both of which matter for interpretation.

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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by tying hosted_only to a specific agent situation ('cannot spawn local tools'), which the schema merely restates as a filter, and by clarifying that verbosity controls the compact per-pick object shape.

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 verb and resource: given a filmmaking brief, return intent-routed MCP recommendations, including the shape of each pick. It does not distinguish itself from near-siblings like get_film_recommendation or plan_film_stack, so an agent must infer the boundary itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete conditional rule ('Use hosted_only=true when the agent cannot spawn local tools') and routes to a named sibling ('get_film_mcp for full server detail'). It stops short of saying when NOT to use this tool versus the other recommendation/planning siblings.

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
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources