Read-only MCP tools for OpenSora video prompt construction, shot planning, diagnosis, and resource discovery.
Four well-named, read-only tools with complete Zod schemas and clear descriptions. All tools follow verb_noun naming (build_, plan_, diagnose_, get_). Descriptions are concise (50 - 150 chars) and explain purpose clearly. Input schemas are fully typed with min/max constraints. However, output schemas are not documented, responses are returned as unstructured text via a generic text() wrapper, forcing LLMs to parse JSON strings rather than receiving structured objects. Tool annotations (readOnlyHint, idempotentHint) are present and correct. Parameter descriptions are adequate but could be more prescriptive about format and constraints. No error handling guidance or recovery paths documented.
Turn a rough video idea into a deterministic prompt pack with motion, camera, lighting, continuity constraints, and revision moves. This does not generate video.
Check whether a video prompt contains a readable scene, visible motion, camera direction, lighting, and continuity controls. Returns focused revision suggestions.
Return canonical OpenSora2.com prompt, workflow, technical, or safety resources. Does not fetch external content.
Break one video idea into 1 to 6 timed shots with purpose, camera direction, and continuity anchors. Read-only and deterministic.
Output schemas not documented. All tools return text via generic text() wrapper; LLMs receive JSON strings to parse rather than structured objects. Breaks pattern:response-shaper and forces token waste on parsing.
Parameter descriptions lack format/constraint details. E.g., 'camera' param says 'Camera movement and framing instructions' but does not specify expected format, length limits (500 chars exist in schema but not in description), or example patterns.
No error handling or recovery guidance. Tools do not document what happens on invalid input (e.g., idea > 5000 chars, shotCount > 6). LLMs receive no actionable error messages or retry hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Limits deployment to local/CLI-only scenarios.
Optional parameters lack clear defaults or dependency hints. E.g., 'camera', 'motion', 'lighting' are optional in build_video_prompt but no guidance on what happens if omitted or how they interact.