Skip to main content
Glama

Generate a new track

generate_track

Compose a brand-new track from Tuney's hand-made musical elements, fitted to an exact length.

    Use exact genre, mood and tempo values from list_styles, or leave them empty for any style.
    Generation runs in the background: this returns a task_id, so call wait_for_task next.
    Previews are free; downloading the final file costs credits.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNo
buildNonone
genreNo
tempoNo
length_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare non-read-only, open-world and non-idempotent behavior, and the description adds genuinely new context beyond them: generation is asynchronous, it returns a task_id, and there is a cost model (previews free, downloads cost credits). The one gap is that it never restates that repeat calls produce distinct tracks, which matters for a non-idempotent generation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with what the tool produces, followed by parameter sourcing, the async workflow and cost. Nothing is repeated from the schema or annotations and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an async, credit-consuming generation tool this covers purpose, chaining and cost; the presence of an output schema means return values need not be detailed in prose. The remaining shortfall is the undocumented 'build' parameter and its default, plus no note on failure behavior of a background task.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning: it covers genre, mood and tempo (including that empty means any style) and hints at length_seconds via 'fitted to an exact length'. It says nothing about the 'build' enum ('none' vs 'ascending') or the 60-second default, leaving two of five parameters unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Compose'), a specific resource ('a brand-new track'), and a distinguishing scope ('fitted to an exact length', 'brand-new' vs. the sibling adjust_track). An agent can tell this apart from adjust_track and find_tracks without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit parameter-sourcing guidance ('Use exact genre, mood and tempo values from list_styles, or leave them empty for any style') and an explicit next step ('call wait_for_task next'). It stops short of stating when to regenerate versus call adjust_track, so it is strong context rather than a full when/when-not decision rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.