Skip to main content
Glama
Hermoso

Hermoso

Official

Generate music

generate_music

Describe a genre, mood, instruments, and tempo to create an instrumental MP3; set seconds for a shorter track or omit length for a full track at a flat fee.

Instructions

RAW music: describe it (genre, mood, instruments, tempo), get an instrumental MP3. No length: a full track at a flat fee (explainerMusicCredits in hermoso_capabilities). With seconds: by the second up to about 38 s. A named model always runs.

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": {
      "prompt": "<prompt>"
    },
    "name": "generate_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNominimax-music-3 or lyria-3.5
promptYesthe music in words, e.g. 'lo-fi jazz, brushed drums, 80 bpm'
secondsNotrack length, up to 300
get_costNotrue: return the price only; nothing runs or bills
idempotency_keyNochosen once, resent unchanged on retries: the same key never buys twice
expected_creditsNothe get_cost price; refused unbilled if the live price differs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.532
    • addedInput schema / properties / expected_credits
      Added value: +{
      +  "description": "the get_cost price; refused unbilled if the live price differs",
      +  "type": "number"
      +}
    • addedInput schema / properties / get_cost
      Added value: +{
      +  "description": "true: return the price only; nothing runs or bills",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "chosen once, resent unchanged on retries: the same key never buys twice",
      +  "type": "string"
      +}
  2. Changed2 schema fields changedv0.1.489
    • addedInput schema / properties / model
      Added value: +{
      +  "description": "minimax-music-3 or lyria-3.5",
      +  "type": "string"
      +}
    • addedInput schema / properties / seconds
      Added value: +{
      +  "description": "track length, up to 300",
      +  "type": "number"
      +}
  3. Addedv0.1.285

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare that this is not read-only, is open-world, and is not idempotent. The description adds billing-mode context and says the output is an instrumental MP3, but its claim that seconds go 'up to about 38 s' conflicts with the schema's 'up to 300', materially misstating the tool's capability. It also omits retry/idempotency behavior that matters for a billed operation.

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 description is short and front-loads the core operation and output. The pricing information is compact, though the 'RAW music' phrasing and the compressed fee sentence are less clear than they could be. No sentence is clearly redundant.

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?

For a six-parameter, billed generation tool with no output schema, the description covers purpose, output type, and pricing modes reasonably well. However, the length contradiction with the schema leaves the agent uncertain about the real seconds limit, and return details are limited to 'instrumental MP3'.

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 coverage is 100%, so every parameter already has a description; the baseline is therefore 3. The description adds some meaning about the seconds-vs-no-seconds tradeoff and that a named model runs, but it does not explain model choice, get_cost, expected_credits, or idempotency_key beyond the schema.

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 operation and output: describe music in words and get an instrumental MP3. It does not name or differentiate from any sibling generation tool, so the agent must infer boundaries from context. The phrase 'RAW music' is unusual but the core purpose is still clear.

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?

It gives useful mode-selection guidance: omit length for a flat-fee full track, or supply seconds for per-second billing. It does not state when to choose this over generate_voice or other siblings, nor any when-not conditions, so it stops short of full alternative routing.

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

Deploy Server

Other Tools