Loading ToolBench
MCP stdio server for remotion-skill-pack — 5 tools for authoring and validating Remotion compositions.
Critical failure across all 6 tools. Descriptions are present but generic (10-60 chars), below the 50-200 char LLM-optimized baseline. No parameter documentation, no output schemas, no error handling guidance. Tools are inferred from filenames rather than explicitly registered with full definitions. This server is non-functional for agent use.
Create a new Remotion composition from scratch or from a template
Generate a Remotion composition from text description
Get a template for a specific scene type
List available Remotion themes
Convert a composition.json to a Remotion TSX project
Validate a Remotion composition against the schema
All 6 tools have empty input schemas (properties: {}). LLMs cannot determine what parameters to pass or their types/constraints.
No parameter descriptions. Tools accept unknown parameters with no guidance on format, constraints, or purpose. E.g., create-composition likely needs 'name', 'template', 'theme' but none are documented.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., composition_id, file_path, theme_list). Breaks tool chaining.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 34 | 2026-07-28+ | v2 |
Descriptions are 10-60 characters (e.g., 'List available Remotion themes'). Even longer ones lack WHEN to use, prerequisites, or return value hints. Baseline is 50-200 chars for LLM optimization.
No error handling or recovery guidance. Tools do not indicate what errors are retryable, user-fixable, or fatal. No actionable error messages documented.