SoundMagic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYTHONPATH | Yes | The path to the project's src directory. | |
| SOUNDMAGIC_ROOT | Yes | The absolute path to the SoundMagic project root. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| soundmagic_capabilitiesA | List installed models, validation status, input paths and complete request schema; does not wake the GPU. |
| soundmagic_submitA | Queue local audio creation/editing and wake an idle worker. Returns a job ID immediately. |
| soundmagic_statusA | Read a job or worker state. Does not wake the GPU or extend the warm timeout. |
| soundmagic_waitA | Wait up to 50 seconds for completion, failure or cancellation. Repeat for long jobs. |
| soundmagic_cancelA | Cancel one queued/running job. Running cancellation terminates its GPU worker. |
| soundmagic_releaseA | Release GPU memory and stop the scheduler after queued/running jobs finish. |
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 6 tools
Each tool has a clearly distinct purpose: capabilities describes the environment, submit creates a job, status checks state, wait blocks for completion, cancel aborts, and release tears down resources. There is no overlap that would cause an agent to misselect.
All tools follow the soundmagic_ prefix and use lowercase snake_case, creating a highly predictable pattern. The action words are mostly verbs (submit, wait, cancel, release) but two are nouns (capabilities, status), a minor deviation from a strictly verb-based scheme.
Six tools is well-scoped for a local audio job manager: discovery, submission, monitoring, waiting, cancellation, and resource release. Each tool earns its place and no redundant utilities are present.
The tool set covers the full lifecycle of a job: check what is possible, submit work, observe progress, wait for a terminal state, cancel if needed, and release the GPU afterwards. No obvious dead ends or missing operations for the stated domain.