Skip to main content
Glama

GenMagic

by io.github.yumaheymans
OverviewDiscussionsAdmin

Generate music

generate_music

Generate an original music track from a text description with GenMagic. Returns the audio inline plus a hosted URL. On-brand in mood automatically when the account has brand personalization on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoOptional GenMagic model id for the music (call list_models with category "audio" for the ids and prices). Omit it to let GenMagic choose its default.
promptYesA description of the music to create (genre, mood, instruments, tempo).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Optional GenMagic model id for the music (call list_models with category \"audio\" for the ids and prices). Omit it to let GenMagic choose its default.",
+  "type": "string"
+}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior beyond structured data: the return shape ('audio inline plus a hosted URL') and an automatic personalization behavior ('on-brand in mood ... when brand personalization is on'). It omits cost, latency, auth/permission needs, and whether generation is synchronous or async.

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?

Three short sentences with no filler, and the core capability plus return format are front-loaded. The trailing personalization sentence is genuinely informative rather than redundant, though it could be folded into the core statement.

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?

With no output schema, the description compensates by describing the return payload (inline audio + hosted URL), and the 100%-covered input schema handles parameters. It leaves an agent without cost/async/auth expectations, but for a two-parameter generation tool it is close to complete.

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 both parameters are already fully documented, including the list_models lookup for model ids. The description adds no syntax, format, or constraint detail beyond what the schema says, so the baseline of 3 applies.

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+resource (generate an original music track from a text description) and immediately scopes it against siblings like generate_image/generate_speech via the word 'music'. An agent can tell instantly what this produces and from what input.

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 implied by 'generate ... from a text description', but there is no explicit when-to-use guidance, no conditions that would steer an agent away, and no named alternative among generate_image/create_video/generate_speech. Sibling coverage exists in the toolset, so the omission matters.

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

All GenMagic toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources