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

character-forge-mcp

by gdhub-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

The voice monologue in another language (paid)

character_voice_translation

Generates a new voice in another language from a translated voice prompt and monologue, so the character's delivery follows its card and the site plays the line in that language.

Instructions

ONLY on request, after character_voice: a new voice in another language, generated from the voice prompt translated by meaning (description + monologue), so the delivery follows the card → voice/reference..mp3, which the site plays in that language. Same price as a line.

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>",
      "lang": "<lang>",
      "text": "<text>"
    },
    "name": "character_voice_translation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
langYes
textYesThe reference monologue translated, keeping its meaning, rhythm, pauses and the character's voice.
descriptionNoThe voice description in that language, translated by meaning. Defaults to the English one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety is partly covered. The description adds real behavioral context the annotations lack: it is a paid operation ('same price as a line'), it depends on prior state, and it writes a file whose path and site-playback behavior are disclosed. Missing: what happens on repeat calls or if the language file already exists.

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?

One tightly packed sentence with the critical constraint ('ONLY on request, after character_voice') front-loaded. The middle clause is somewhat run-on, but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid generation tool with no output schema, the description usefully names the output file location and price. However it omits the semantics of the required 'id' parameter, the fact that only 'ru' is currently allowed despite the generic 'another language' phrasing, and error/rate behavior for a paid call.

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 coverage is 50%: text and description are documented in-schema, while id and lang are not. The description does clarify the meaning-based translation of description plus monologue, which maps those two parameters to their purpose. But 'id' is never explained (presumably a character id) and the language scope is only implied by the title, so it does not fully compensate for the coverage gap.

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?

States a concrete action: generate a new voice in another language from the voice prompt translated by meaning, and names the artifact it produces (voice/reference.<lang>.mp3). It links itself to the sibling character_voice as a prerequisite, which helps distinguish it. The phrasing 'a new voice in another language' is slightly compressed but unambiguous in context.

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?

Gives an explicit gate: 'ONLY on request, after character_voice,' so the agent knows both the trigger condition and the required prior call. It does not enumerate when-not cases beyond that, nor what to do if character_voice was never run, but the core routing guidance is present.

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