Tunova
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TUNOVA_API_KEY | Yes | Your Tunova API key. Get one at https://tunova.ai |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_songA | Start generating a song with Suno. Returns immediately with a job_id — a full render takes 1-3 minutes, so this does NOT return audio. After calling this, call wait_for_song with the returned job_id to get the audio URL when ready. Costs 10 tokens, billed only on success. |
| wait_for_songA | Wait for a song job to finish and return the audio when ready. Polls server-side for up to ~45 seconds. If the song is ready, returns the clips with audio URLs. If it is still rendering, returns its status so you can call wait_for_song again with the same job_id. Safe to call repeatedly — it only reads status, never starts a new song. |
| check_songA | Get the current status of a song job by job_id — a single check with no waiting. Returns the audio URLs if complete, an error if it failed, or 'processing' if still rendering. |
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 3 tools
Each tool has a clearly distinct role: generate_song starts a job, check_song provides a one-time status check, and wait_for_song polls until completion. The overlap between check_song and wait_for_song is minor since one is a single check and the other is a polling loop.
All tool names follow a consistent verb_noun pattern with underscores (check_song, generate_song, wait_for_song), making the set predictable and easy to navigate.
Three tools is well-scoped for the server's single purpose of generating songs, covering initiation, status checking, and waiting. Each tool is necessary and there is no bloat.
The toolset fully covers the song generation workflow: start a job (generate_song), check status (check_song), and retrieve audio after waiting (wait_for_song). There are no obvious gaps like missing cancellation or listing, which are not necessary for this narrow domain.