ofaudio-mcp

save_voice

Save a previewed voice as a permanent reusable voice for future speech generation. Provide a name and the preview ID to secure your custom voice slot.

Instructions

Save a designed voice preview (from design_voice) as a permanent, reusable voice.

Consumes one custom-voice slot on the account. After this, generate_speech(voice="") uses it.

Args: name: Handle to save under. generated_voice_id: The preview id from design_voice. description: Optional description stored on the voice.

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": {
      "name": "<name>",
      "generated_voice_id": "<generated_voice_id>"
    },
    "name": "save_voice"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`description`	No
`generated_voice_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description discloses the key side effect: it consumes one custom-voice slot. It also clarifies that the saved voice becomes available to generate_speech. It doesn't mention overwrite behavior or reversibility, but covers the main behavioral contract.

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?

The description is concise and well-structured: a one-line purpose, a two-sentence behavioral note, and a compact Args list. Every sentence adds value with no redundancy.

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?

For a tool with no annotations and no output schema, the description gives a complete picture: where the input comes from, what side effect occurs (slot consumption), and how the result is used later (with generate_speech). All parameters are explained, and the tool's place in the broader workflow is clear.

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 coverage is 0%, so the description must explain parameters. It does so fully: 'name' is the handle to save under, 'generated_voice_id' is the preview id from design_voice, and 'description' is optional metadata stored on the voice. This adds clear meaning beyond the bare schema titles.

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?

The description clearly identifies the specific action (saving a designed voice preview) and its resource (from design_voice, as a permanent reusable voice). It distinguishes the tool from siblings like delete_voice and list_voices by tying it to the design->save->generate workflow.

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?

The description provides clear context: it should be used after design_voice and before generate_speech. It explains the prerequisite and downstream usage, but doesn't explicitly name alternatives or state when not to use it.

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