Skip to main content
Glama
Sign In

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

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.9/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, non-idempotent and non-destructive, so the safety profile is covered. The description adds real value beyond that: the return shape (inline audio plus hosted URL) and the implicit brand-personalization behavior that changes output without any parameter. It stops short of noting that each call is a fresh, billed generation.

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 the core action front-loaded and the return format immediately after; nothing is buried. 'with GenMagic' is slight branding filler, keeping it just under a perfect score.

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?

For a two-parameter generation tool with no output schema, the description covers what matters most: the input is text, the output is audio plus a URL, and brand personalization can alter results. Cost and latency, hinted at by the list_models price reference in the schema, are the main omissions.

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 prompt and model are already documented with examples of what to include. The description only echoes 'from a text description' and adds no syntax, length, or model-default guidance beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 ('Generate an original music track from a text description') and names the provider, which cleanly separates it from the audio-adjacent siblings like generate_speech and generate_image. An agent can tell exactly what modality and output this produces without opening the schema.

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 modality contrast with siblings; the description never states when to prefer this over generate_speech or create_video, nor any exclusions or prerequisites. The only alternative-routing guidance (call list_models for model ids) lives in the schema, not the description.

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