character-forge-mcp

Overview Schema Source Related Servers Discussions Admin

Save a translation of the card

character_translate

Translate a character card's free-text fields into another language and save the result as card..json beside the English source while keeping structure, IDs, numbers, enums, and colors intact.

Instructions

When the user asked for other languages: saves the card translated (e.g. lang 'ru') as card..json next to the English original, which stays the source. Translate every free-text field in the character's own voice, as the editor would write it in that language; keep the structure, list lengths, numbers, ids, enums and colours exactly.

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>",
      "card": "<card>"
    },
    "name": "character_translate"
  }
}

Input Schema

Name	Required	Description
`id`	Yes
`card`	Yes
`lang`	Yes	Language code, e.g. 'ru'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Nov 12, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behavior: it writes card.<lang>.json next to the English original, keeps the original as source, and requires preserving structure, list lengths, numbers, ids, enums and colours. It omits overwrite behavior and error conditions, but is substantially transparent for a save operation.

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?

The description is front-loaded with the trigger condition and the core action, then details the translation constraints. It is dense but every clause earns its place; no unnecessary repetition.

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?

Given the very large nested card schema, no output schema and no annotations, the description covers the essential translation rules well. It is still incomplete regarding the id parameter's meaning and what happens if a translation file already exists.

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 low at 33%, so the description must compensate. It adds meaning for lang (example 'ru') and for card (translate every free-text field, preserve structural details), but does not explain the required id parameter.

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?

The description states a specific verb and resource: saves the card translated as card.<lang>.json next to the English original. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as character_voice_translation or character_save.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives a condition for use ('When the user asked for other languages'), which implies the right context. However, it does not name alternatives or state when not to use this tool, so guidance remains implicit.

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