see-dance-2-prompt-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_seedance_promptB | Turn a rough idea into a deterministic English or Chinese prompt with separate subject and camera motion, exact reference bindings, and continuity controls. |
| plan_reference_sequenceA | Create a deterministic 1–6 shot sequence with exact reference bindings, timing, continuity anchors, and end frames. |
| diagnose_seedance_promptA | Check English or Chinese prompts for visible motion, camera direction, lighting, continuity, and preserved reference tokens. |
| get_see_dance_2_resourcesB | Return canonical See Dance 2 prompting, workflow, reference, 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 clear, distinct role: building a prompt, planning a sequence, diagnosing issues, and fetching resources. There is no overlap in purpose, making selection unambiguous.
All tools follow a consistent verb_noun pattern using snake_case, with clear action prefixes (build, plan, diagnose, get). The naming is uniform and predictable.
Four tools is an appropriate scope for this domain, covering the core workflow without redundancy or excessive granularity. Each tool earns its place.
The toolset covers the full lifecycle: creating a prompt, planning sequences, diagnosing problems, and accessing resources. There are no obvious missing operations for the stated purpose.