Skip to main content
Glama
Sign In
character-forge-mcp

character-forge-mcp

by gdhub-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Design the character's voice (on request, paid)

character_voice

Creates a character's voice from a written description and reference monologue, then records the same voice in requested languages for story-ready audio.

Instructions

ONLY on request; confirm the cost first. Creates the character's own voice from a description and an English reference script (write both with character_prompt kind 'voice'), plus any other languages listed in translations, each performed from the same description. Adults: ElevenLabs Voice Design, a saved voice and its reference take (≈$0.10 per 1000 characters of the script). Under 18: Qwen 3 Voice Design, deepened by pitch_semitones and cloned into a speaker embedding (≈$0.03). Saves assets/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": {
      "id": "<id>",
      "description": "<description>",
      "text": "<text>"
    },
    "name": "character_voice"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
textYesReference script: their inner monologue in the moment the scene shows, thoughts to themselves, never addressed to the listener; natural voice, not a whisper. Eleven v3 tags like [sighs] are allowed; they are dropped for minors.
descriptionYesWho they are and how they sound: history, how they talk and to whom, then age, gender, timbre, pace, recording.
translationsNoOther languages to record in the same call, each performed fresh from the description (not a copy of the English take) → voice/reference.<lang>.mp3.
pitch_semitonesNoMinors only: deepen (negative) or lighten the designed voice. Default -2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses per-provider pricing, age-based routing (ElevenLabs for adults, Qwen 3 for minors with pitch deepening and cloning), that v3 tags are dropped for minors, and where assets land. It does not say what happens to a pre-existing voice, whether generation is idempotent, or how failures/long runtimes behave.

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 dense sentences with the gating condition and prerequisite front-loaded, and cost/artifact facts packed parenthetically rather than sprawled. The trailing 'Saves assets/voice/' is telegraphic but informative; nothing is filler.

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 paid mutation with no annotations and no output schema, the description covers the cost model, the input-authoring prerequisite, the age-based engine choice, and the written outputs. The notable remaining gap is the return value (e.g., saved voice id or handle) needed to chain into later voice-line calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3; the description earns above that by explaining that translations are each performed fresh from the description rather than copied from the English take, and by tying text/description to the character_prompt 'voice' workflow. The pitch_semitones minors-only note largely restates the schema, but the cross-parameter relationship (same description driving all takes) is genuine added meaning.

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 artifact: it 'Creates the character's own voice from a description and an English reference script', performed per language listed in translations, and names the destination assets/voice/. The phrase 'own voice' plus the description-and-script inputs separates it from line-level or translation-in-place siblings without needing to name them.

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?

Gives an explicit gate ('ONLY on request; confirm the cost first') and a prerequisite step ('write both with character_prompt kind "voice"'), which is exactly the when-and-how guidance an agent needs before calling a paid generator. It also implicitly scopes translation work into this single call rather than a separate one.

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

Deploy Server

Other Tools