Skip to main content
Glama

GenMagic

by io.github.yumaheymans
OverviewDiscussionsAdmin

Generate speech (text to speech)

generate_speech

Turn text into spoken audio with GenMagic. Returns the audio inline plus a hosted URL. The text is voiced verbatim.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesThe text to speak, read aloud verbatim.
modelNoOptional GenMagic model id for the speech (call list_models with category "audio" for the ids and prices). Omit it to let GenMagic choose its default.
voiceNoOptional voice name (e.g. alloy); list_models shows each speech model's voices. Defaults to a neutral voice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / model
      Added value: +{
+  "description": "Optional GenMagic model id for the speech (call list_models with category \"audio\" for the ids and prices). Omit it to let GenMagic choose its default.",
+  "type": "string"
+}
    • changedInput schema / properties / voice / description
      Previous value: -"Optional voice name (e.g. alloy). Defaults to a neutral voice."New value: +"Optional voice name (e.g. alloy); list_models shows each speech model's voices. Defaults to a neutral voice."
  2. First observed

TDQS

A3.8/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 return behavior ('audio inline plus a hosted URL') and the verbatim voicing contract, which is genuinely useful; however it says nothing about authentication requirements, cost/credits, rate limits, or whether the hosted URL expires, leaving meaningful behavioral gaps.

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?

Three short sentences with no waste; the core purpose is front-loaded and the return value and voicing contract follow immediately. Every sentence carries information.

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 appropriately covers the return shape (inline audio plus hosted URL), and the 100%-covered input schema handles parameters. Only thin on operational context such as cost or auth, which for a simple generation tool is a minor omission.

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 all three parameters (input, model, voice) are already documented with defaults and cross-references to list_models. The description's 'voiced verbatim' only loosely reinforces the input semantics and adds no syntax or format detail beyond the schema.

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 ('Turn text into spoken audio') plus the provider, and the spoken-audio modality cleanly separates it from generate_music, generate_image, generate_video, and generate_text in the sibling set. An agent can pick it 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?

No explicit when-to-use or when-not-to-use statement and no named alternative, but the purpose sentence plus 'voiced verbatim' implies the use case (verbatim narration rather than music or generic text). Usage is inferable rather than stated.

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