Skip to main content
Glama

Text To Music Price

text_to_music_price

Calculate the price of text-to-music generation before running a job. Enter a model, duration in seconds, and optional inference steps to get the estimated cost.

Instructions

Calculate price for text-to-music generation.

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 observedv0.6.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about whether the call is free, whether it consumes credits, whether it is read-only, or how pricing is derived. For a pricing tool where cost/side-effect expectations matter, this is a meaningful gap.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than optimal conciseness.

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

Completeness3/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 parameters are documented in the schema. However, with no annotations and no behavioral context about pricing or side effects, the definition is only minimally complete for an agent deciding whether and how to call it.

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 100%, so model, duration, and inference_steps are already documented in the schema, including the 10-600 second bound and the 'leave unset when the model fixes it' note. The description adds no meaning beyond that, so the baseline of 3 applies.

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 description states a specific verb and resource: 'Calculate price for text-to-music generation.' This clearly separates it from the generation sibling text_to_music and from other pricing siblings such as text_to_image_price, though it never names an alternative explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. that a model must be chosen first), and no reference to alternatives. Usage is only implied by the tool name and the word 'price'.

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