Skip to main content
Glama

Kubeez

generate_music_persona

Idempotent

Scope: generate:music. Create a reusable PERSONA from a song you already generated, capturing its voice and style. Synchronous and FREE: returns the persona in one call (no polling). Inputs: song_id (a music_songs id from get_status on a completed music generation), name (<=80 chars), description (<=500 chars; the voice/mood/genre to capture), optional style tag. Requirements: the source song must be fully generated on a model above v3.5 (all current models qualify); each song can only have ONE persona (a repeat call returns the existing one). Use the returned persona_id with generate_music(persona_id=...) to sing new songs in that identity.

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": {
      "song_id": "<song_id>",
      "name": "<name>",
      "description": "<description>"
    },
    "name": "generate_music_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
styleNo
song_idYes
descriptionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it declares the call is synchronous with no polling, that it is free, that each song can only have one persona and a repeat call returns the existing one (sharpening the idempotentHint into concrete behavior), and that the source model must exceed v3.5. These are exactly the operational facts an agent needs and none are duplicated from structured fields.

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?

Front-loaded with scope and purpose, then labeled Inputs and Requirements sections. Every clause carries information (cost, sync behavior, caps, preconditions, follow-up usage) with no filler despite the density.

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

Completeness5/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 the description covers the remaining gaps: cost, synchronicity, model eligibility, uniqueness constraint, and how to consume the result. Nothing an agent needs in order to call this correctly is missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: song_id is tied to a music_songs id obtained from get_status on a completed generation, name is capped at 80 chars, description is capped at 500 chars and defines what to express (voice/mood/genre), and style is marked optional. Every parameter gains meaning the bare schema lacks.

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 and resource ('Create a reusable PERSONA from a song you already generated') and immediately clarifies what is captured ('voice and style'), which distinguishes it from the sibling generate_music that produces songs. An agent can tell this is a derived-asset creation step, not a generation job.

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 concrete preconditions ('source song must be fully generated on a model above v3.5') and an explicit next step ('use the returned persona_id with generate_music(persona_id=...)'). It stops short of naming sibling alternatives such as list_music_personas for inspection, so it is clear context rather than complete when/when-not routing.

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.

Resources