Skip to main content
Glama
Buggy1111

anonymize-mcp

by Buggy1111
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

translate_text

Translate text between 8 languages using Charles Translator, with direct pairs and automatic English pivot for unsupported language pairs. Supports document mode for preserving structure in Czech-English translations.

Instructions

Přeloží text přes Charles Translator (LINDAT) — 8 jazyků, 17 přímých párů + auto EN-pivot pro nepřímé páry.

Podporované jazyky: ``cs`` (čeština), ``en``, ``fr``, ``de``, ``pl``,
``ru``, ``uk`` (ukrajinština), ``hi`` (hindština).

**Přímé páry** (17): cs↔en (+doc), cs↔uk, cs↔ru, en↔fr, en↔de, en↔ru,
en↔pl, en→hi (jednosměrně).

**EN-pivot** (auto): pro páry mimo seznam (typicky de→cs, pl→cs, fr→cs,
fr→de) wrapper provede 2 volání ``src→en→tgt`` a vrátí finální překlad
+ warning + ``pivot=True``. Doc-mode v pivotu nepodporován.

Klíčové páry pro legal-tech:
- ``cs-en`` / ``en-cs`` — anglické sumáře, mezinárodní komunikace
- ``doc-cs-en`` / ``doc-en-cs`` (s ``document_mode=True``) — celé dokumenty
  se zachovanou strukturou odstavců
- ``cs-uk`` / ``uk-cs`` — ukrajinští klienti / legal aid pro UA migranty
- ``cs-ru`` / ``ru-cs`` — ruskojazyční klienti
- ``de-cs`` / ``pl-cs`` / ``fr-cs`` — automatický EN-pivot pro EU sousedy

Pozor: SK ↔ CZ pár v Charles Translatoru chybí. SK je auto-alias na CS
(mutual intelligibility). HI lze jen jako tgt (en→hi), ne jako src.

Charles Translator umí vlastní jména zachovat v originále — užitečné
pro legal: *"Jiří Pluhařík podal žalobu u Krajského soudu v Ostravě."*
→ *"Jiří Pluhařík filed a lawsuit at the Krajský soud v Ostrava."*

Args:
    text: Text k překladu (UTF-8).
    src: Zdrojový jazyk (default ``cs``).
    tgt: Cílový jazyk (default ``en``).
    document_mode: True pro doc mode (cs↔en only). Zachová strukturu.

Returns:
    ``translated`` (přeložený text), ``src``, ``tgt``, ``pair``
    (skutečně použitý model name), ``document_mode``, ``input_chars``,
    ``output_chars``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
srcNocs
tgtNoen
document_modeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Discloses pivot behavior (two API calls, warning, pivot flag), document mode restrictions, proper noun preservation, and language pair specifics. No annotations provided, so description carries full burden and does so thoroughly without contradictions.

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 long but well-structured with sections for languages, direct pairs, pivot, legal-tech examples, Args, and Returns. Every sentence adds value, though slight redundancy in language listing. Front-loaded with essential info.

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?

Given output schema listing return fields, description still covers Returns as a bonus. Covers all necessary context: supported pairs, pivot mode, document mode, limitations, proper noun handling, and usage tips. Complete for a translation tool.

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 has 0% coverage, but description compensates by explaining each parameter in Args section, including defaults and context (e.g., document_mode only works for cs↔en). Adds meaning beyond 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?

The description clearly states the tool translates text via Charles Translator, supporting 8 languages and 17 direct pairs plus auto EN-pivot. It distinguishes well from sibling tools like extract_entities or correct_text by focusing on translation.

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?

Provides explicit guidance on when to use direct pairs vs pivot, legal-tech use cases, limitations (e.g., SK-CZ missing, HI only as target), and document mode scope. Answers when to use and when not.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Buggy1111/anonymize-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server