Skip to main content
Glama

Generate audio

generate_audio

Submit a speech generation request through Rainbrand’s public API. Use a supported audio model returned by list_models and follow its published input schema from get_model. Use relevant brand context to write the text to speak. Returns the generation ID and its current status. Inspect the result with get_generation.

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": {
      "brand_session_id": "<brand_session_id>",
      "model": "<model>",
      "input": "<input>"
    },
    "name": "generate_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesArguments for the selected model, using the field names and reference formats published by get_model.
modelYesModel to run. Choose an ID from list_models whose output type matches the generation tool being called.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
idempotency_keyNoRetry key for recovering the original generation after an uncertain response. Reuse it with identical arguments. Without a key, repeating the request starts another generation.
brand_session_idYesBrand session ID from list_brands for the brand this generation belongs to.

Output Schema

NameRequiredDescriptionDefault
idYesGeneration ID. Pass it as id to get_generation.
statusYesCurrent generation status.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnlyHint=false, openWorldHint=true, idempotentHint=false, so the write-and-non-idempotent profile is covered structurally. The description adds real value by disclosing that the call is asynchronous ("Returns the generation ID and its current status") and by pointing to get_generation for the result, which is behavior not visible in the annotations. It omits any mention of credit consumption or retry semantics, which the schema carries instead.

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?

Four short sentences, front-loaded with the action and then the workflow steps; nothing is redundant. The instruction "Use relevant brand context to write the text to speak" edges toward prompt-engineering advice rather than tool definition, keeping it just below full marks.

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 5-parameter mutation with a nested free-form input object and an existing output schema, the description covers the prerequisite model lookup, the schema source for input, and the follow-up retrieval step. The open-ended nested input is delegated explicitly to get_model, which is the right strategy, so what remains is minor.

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 every parameter including the nested input object is already documented in the schema. The description adds only loose context ("Use relevant brand context to write the text to speak" and referencing list_models for the model value), which marginally reinforces the schema rather than extending it. Baseline 3 applies.

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 verb and resource ("Submit a speech generation request") and narrows it to speech, which implicitly separates it from generate_image and generate_video siblings. It does not explicitly name those alternatives, so the differentiation is inferred from the modality word rather than stated.

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 a clear call sequence: pick a model via list_models, follow the input schema from get_model, then inspect with get_generation. There is no explicit when-not-to-use guidance (for example, when to use generate_image or generate_video instead), so it falls short of full routing guidance.

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