seevido
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEEVIDO_APP_BASE_URL | No | Base URL for canonical resource links. Only set when links should use another origin. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| build_video_promptB | Turn a rough idea into a deterministic English or Chinese prompt pack with motion, camera, lighting, reference roles, and continuity controls. |
| plan_reference_sequenceB | Create a deterministic 1–6 shot sequence with reference roles, timing, continuity anchors, and intended end frames. |
| diagnose_video_promptA | Check English or Chinese prompts for scene, motion, camera, lighting, continuity, and preserved reference tokens. |
| get_seevido_resourcesA | Return canonical SeeVido prompting, workflow, model-orientation, or safety resources without fetching external content. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: building prompts, planning sequences, diagnosing prompts, and retrieving resources. There is no overlap in functionality, so an agent can clearly identify which tool to use for a given task.
All tool names follow the verb_noun pattern in snake_case (build_video_prompt, plan_reference_sequence, diagnose_video_prompt, get_seevido_resources). The verbs clearly describe the action and the nouns the target, making the naming predictable and uniform.
With exactly 4 tools, the server is well-scoped and each tool earns its place for the domain of video prompt engineering. This is within the ideal 3-15 range and not excessive for the functionality offered.
The tools cover the core lifecycle of video prompt creation: building, planning sequences, diagnosing, and obtaining resources. Minor gaps exist, such as no tool for editing or deleting existing prompts, but these are not essential for the server's apparent purpose and agents can work around them.