VoiceStudio MCP

Official

Overview Schema Source Related Servers Discussions Admin

describe_voice

Preview how free-text voice descriptions map to supported design attributes (gender, age, pitch, accent) before generating a voice; unmatched terms are reported.

Instructions

Preview how a voice description maps onto voice-design attributes.

    Nothing is saved. Use this before design_voice to see what the
    description will produce. The design space is small and fixed; only
    these tokens (and close synonyms) are understood:
      Gender: male, female
      Age: child, teenager, young adult, middle-aged, elderly
      Pitch: very low / low / moderate / high / very high pitch
      Style: whisper
      EnglishAccent: american, british, australian, canadian, indian,
        japanese, korean, chinese, russian, portuguese accent
      ChineseDialect (Chinese speech; overrides an English accent):
        sichuan, dongbei / northeastern chinese, henan, shaanxi, gansu,
        guilin, guizhou, jinan, ningxia, qingdao, shijiazhuang, yunnan
        (e.g. "sichuan dialect")
    Timbre words ("gravelly", "raspy") and other accents are ignored and
    reported in `unmatched`. For a voice outside this space, use
    clone_voice with reference audio instead.

    Args:
        description: Free-text description, e.g. "an elderly man with a
            deep voice and a british accent".

    Returns:
        JSON with attrs (category → token or "Auto"), instruct, matched
        and unmatched.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`description`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

No annotations are present, so the description carries the full burden, and it does: 'Nothing is saved' declares the non-mutating nature, the fixed token vocabulary declares the input constraints, and the ignored-timbre behavior is disclosed along with where it surfaces ('reported in `unmatched`'). That is more side-effect and constraint disclosure than most annotated tools provide.

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?

Front-loaded with the purpose and the safety fact before the long but necessary token enumeration. Slight waste in the boilerplate 'Args:'/'Returns:' blocks, the latter of which restates an output schema that already exists, but the token list is essential for correct invocation.

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 single-parameter preview tool with no annotations, the description supplies the purpose, the safety profile, the accepted vocabulary, the fallback tool, and the output shape. Nothing an agent needs to invoke it correctly or interpret the result is missing.

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 description coverage is 0% for the single required parameter, so the description must compensate, and it does with a concrete format example ('an elderly man with a deep voice and a british accent') plus the full vocabulary of understood tokens and the fact that out-of-vocabulary words are ignored rather than rejected.

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 (preview) plus the transformation it performs — mapping a free-text voice description onto design attributes — and implicitly distinguishes itself from design_voice (the committing sibling) and clone_voice (the out-of-space fallback). An agent can tell exactly what this tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing: 'Use this before design_voice to see what the description will produce.' Explicit exclusion with a named alternative: 'For a voice outside this space, use clone_voice with reference audio instead.' Both the when-to-use and when-not-to-use paths are covered.

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