Arckép

design_speech_voice

Create a custom voice from a text description. Free; the voice lives 365 days.

request: display_name, prompt (10-1000 characters: age, timbre, pace, manner, accent), gender (male, female or neutral) and optional language_code (default ru-RU). The result holds the voice (use its id as custom_voice_id in create_speech) and a short sample. An account keeps at most 5 saved voices (made here or in the studio; expired ones do not count): the sixth fails with 409 VOICE_LIMIT_REACHED, details.limit and details.used, and delete_speech_voice makes room. Google also caps the whole project at 200 voices (the same 409). One creation per account at a time: a parallel one fails with 429 VOICE_CREATION_IN_PROGRESS, wait and retry. There is no idempotency key: after a timeout check list_my_speech_voices before retrying, and remove an extra voice with delete_speech_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": {
      "request": "<request>"
    },
    "name": "design_speech_voice"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only mark it as a non-read-only, non-destructive write; the description carries far more: cost (free), 365-day lifetime, a per-account cap of 5 with 409 VOICE_LIMIT_REACHED plus details.limit/details.used, a project-wide cap of 200, single-concurrency 429, and the absence of an idempotency key with timeout-recovery steps.

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 purpose and cost, then escalating operational detail; every clause carries a fact an agent needs (limits, error codes, retry path). It is dense and parenthetical-heavy, but there is no filler to cut.

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?

Despite an output schema existing, it briefly says what the result contains (the voice entity and a sample) and how to consume it downstream. Quota, concurrency, failure codes, and recovery are all covered, so an agent can call it correctly without further lookups.

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 reported as 0%, so the description must compensate, and it does: it enumerates display_name, prompt (with 10-1000 char bound and what to encode: age, timbre, pace, manner, accent), the gender enum values, and a default of ru-RU for language_code that appears nowhere in 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?

Opens with a specific verb+resource: 'Create a custom voice from a text description.' This is clearly distinct from create_speech (synthesis) and replicate_speech_voice (cloning) among the siblings, and it also states the artifact's lifetime up front.

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?

Explicitly states when to use it (designing a voice from a prompt before synthesis, via 'use its id as custom_voice_id in create_speech') and names the alternatives for each failure mode: delete_speech_voice to free a slot, list_my_speech_voices to check before retrying.

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

All Arckép tools Inspect

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.