Skip to main content
Glama

Text To Music Price

text_to_music_price

Calculate price for text-to-music generation.


Available models:

  • MiniMaxMusic3_11B_INT8: steps=30 (fixed), guidance=1.7 (fixed), duration=20-300s, bpm=30-30, caption=3-2000 chars, ref_audio=0s (fixed)

  • AceStep_1_5_XL_Turbo_INT8: steps=8 (fixed), guidance=1 (fixed), duration=10-300s, bpm=50-200, caption=3-300 chars, ref_audio=5-60s

  • AceStep_1_5_Turbo: steps=8 (fixed), guidance=1 (fixed), duration=10-300s, bpm=50-200, caption=3-300 chars, ref_audio=5-60s

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "model": "<model>",
      "duration": "<duration>"
    },
    "name": "text_to_music_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesMusic generation model name
durationYesAudio duration in seconds, as the job will send it
inference_stepsNoInference steps. Leave unset when the model fixes it

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does add real value by publishing per-model constraints: fixed inference_steps and guidance, duration ceilings of 20-300s vs 10-300s, bpm ranges, caption length limits, and ref_audio bounds. However, it never states that this is a pure, side-effect-free calculation (no job submitted, no credits consumed), which is the single most important behavioral fact for a pricing tool.

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

Conciseness4/5

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

The one-line purpose is front-loaded and the per-model constraints are presented as a scannable list rather than prose. The repeated 'fixed' annotations for steps and guidance are slightly redundant, but overall the structure is efficient for the amount of constraint data conveyed.

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?

An output schema exists, so return values need not be explained, and all three parameters are fully described in the schema. What remains missing is the relationship to text_to_music (that this is a pre-flight estimate) and the 600-vs-300 duration discrepancy, but for a three-parameter pricing call the definition is largely sufficient.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, and the description earns above that by giving model-specific duration and inference_steps rules that the schema cannot express (it only allows a flat 10-600s duration). One inconsistency: the schema permits duration up to 600 while every listed model caps at 300, and MiniMaxMusic3 shows 'bpm=30-30', which reads as a typo and could mislead.

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

Purpose4/5

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

The opening line states a specific verb and resource ('Calculate price for text-to-music generation'), which separates it from the generation sibling text_to_music. It does not explicitly say 'this is an estimate only, no job is created', but the 'price' framing makes the distinction clear enough to route correctly.

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

Usage Guidelines3/5

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

Usage is only implied by the name and first sentence; there is no explicit 'call this before text_to_music' or 'use when you need a cost estimate without generating audio'. The per-model table implicitly tells the agent which models are valid and their limits, but no when-not-to-use or alternative routing is stated.

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.