mcp-media-orchestrator
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_capabilitiesA | List every model this server can route to, with cost and latency. |
| generate_mediaA | Start a generation and return a job handle. Returns immediately. The job is not finished when this returns; poll get_job with the returned job_id until state is one of succeeded, failed, cancelled or rejected. Set backend only to pin a specific provider. Leaving it unset lets the server route, which is normally what you want. |
| get_jobB | Read the current state of a generation job. |
| cancel_jobA | Cancel a running job. Best effort provider-side, always terminal here. |
| list_jobsB | List recent jobs, newest first, optionally filtered by state. |
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 5 tools
Each tool maps to a distinct part of the media generation workflow: capability discovery, job submission, status polling, cancellation, and history listing. There is no meaningful overlap or risk of selecting the wrong tool for a given operation.
All tool names follow a consistent verb_noun pattern using snake_case: list_capabilities, generate_media, get_job, cancel_job, list_jobs. The verbs clearly indicate the action and the nouns clearly indicate the target resource.
Five tools is well-scoped for an orchestration server handling asynchronous media generation. Each tool covers a necessary part of the workflow without redundant or excessive surface area.
The toolset covers the full asynchronous job lifecycle: discover capabilities, create a job, poll for completion, cancel if needed, and list past jobs. There are no obvious dead ends for the stated purpose of routing and orchestrating media generation.