Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

translate

Convert text between languages with automatic detection, context-aware output, glossaries, and translation memories. Accepts one target language per call.

Instructions

Translate text between languages using Lara Translate. Supports language detection, context-aware translations, translation memories, and glossaries. The optional 'instructions' parameter accepts short localization directives (e.g., 'Translate formally') — only provide them when the content specifically requires tone, formality, or terminology adjustments. IMPORTANT: 'target' accepts exactly one language code per call. If the user asks to translate into multiple languages (e.g., 'into Italian and German'), call this tool once per target language and present all resulting translations together. IMPORTANT: 'glossaries' requires glossary IDs in the 'gls_*' format, not glossary names. If the user refers to a glossary by name (e.g., 'our company glossary', 'the marketing glossary'), call list_glossaries first, match the name, and use the returned ID here. If no matching glossary is found, tell the user instead of guessing an ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesAn array of text blocks to translate. Each block contains a text string and a boolean indicating whether it should be translated. This allows for selective translation where some text blocks can be preserved in their original form while others are translated.
styleNoControls how the translation balances accuracy against natural readability. 'faithful' stays close to the source, 'fluid' prioritizes natural readability, 'creative' allows more freedom in the translation.
sourceNoThe source language code (e.g., 'en-EN' for English). If not specified, the system will attempt to detect it automatically. If you have a hint about the source language, you should specify it in the source_hint field.
targetYesThe target language code (e.g., 'it-IT' for Italian). This specifies the single language you want the text translated into. This field accepts ONE language code only. If the user wants the text translated into multiple languages, call this tool once per target language.
contextNoAdditional context string to improve translation quality (e.g., 'This is a legal document' or 'Im talking with a doctor'). This helps the translation system better understand the domain.
adapt_toNoA list of translation memory IDs (format 'mem_*') for adapting the translation. If the user refers to a memory by name rather than by ID, call list_memories first to resolve the name to its ID before calling this tool.
no_traceNoPrivacy flag. If set to true, the request content will not be stored or traced by Lara. Use for sensitive content.
priorityNoTranslation priority. 'normal' for real-time translations, 'background' for batch processing with lower priority.
reasoningNoEnables Lara Think multi-step linguistic analysis. Can increase processing time up to 10x but may improve translation quality for complex texts.
glossariesNoArray of glossary IDs to apply during translation (max 10). IDs must match format: gls_* (e.g., ['gls_xyz123', 'gls_abc456']). Glossaries enforce specific terminology and terms. If the user refers to a glossary by name rather than by ID (e.g., 'my company glossary'), call list_glossaries first to resolve the name to its ID before calling this tool.
source_hintNoUsed to guide language detection. Specify this when the source language is uncertain to improve detection accuracy.
content_typeNoSpecifies the content type of the text. Autodetected if omitted.
instructionsNoOptional list of short localization directives to adjust translation output. Each instruction MUST be no more than 20 words. These are NOT free-form LLM prompts — they are expert localization directives about formality, tone, or domain-specific terminology. Only provide instructions when the content specifically requires them; omitting instructions for general content preserves higher translation quality. Do NOT combine contradictory instructions (e.g., formal and informal tone together). Examples: 'Translate formally', 'Use a creative and concise tone', 'Make translation gender-neutral', 'Mask any price with the [price] placeholder', 'Use quotation marks (« ») for quotations'.
timeout_in_millisNoCustom timeout for the translation request in milliseconds. Max: 300000ms (5 minutes). Useful for very long texts.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesTranslated text blocks, in the same order and structure as the input. Blocks marked translatable: false are preserved verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.0.0
    • changedInput schema / properties / adapt_to / description
      Previous value: -"A list of translation memory IDs for adapting the translation."New value: +"A list of translation memory IDs (format 'mem_*') for adapting the translation. If the user refers to a memory by name rather than by ID, call list_memories first to resolve the name to its ID before calling this tool."
    • changedInput schema / properties / glossaries / description
      Previous value: -"Array of glossary IDs to apply during translation (max 10). IDs must match format: gls_* (e.g., ['gls_xyz123', 'gls_abc456']). Glossaries enforce specific terminology and terms."New value: +"Array of glossary IDs to apply during translation (max 10). IDs must match format: gls_* (e.g., ['gls_xyz123', 'gls_abc456']). Glossaries enforce specific terminology and terms. If the user refers to a glossary by name rather than by ID (e.g., 'my company glossary'), call list_glossaries first to resolve the name to its ID before calling this tool."
    • changedInput schema / properties / target / description
      Previous value: -"The target language code (e.g., 'it-IT' for Italian). This specifies the language you want the text translated into."New value: +"The target language code (e.g., 'it-IT' for Italian). This specifies the single language you want the text translated into. This field accepts ONE language code only. If the user wants the text translated into multiple languages, call this tool once per target language."
    • removedInput schema / properties / text / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / items / items / additionalProperties
      Removed value: -{}
  2. Changed5 schema fields changedv1.0.4
    • changedInput schema / properties / text / items / additionalProperties
      Previous value: -falseNew value: +{}
    • addedInput schema / properties / text / items / properties / text / description
      Added value: +"Text content of the block"
    • addedInput schema / properties / text / items / properties / translatable / description
      Added value: +"Whether the block should be translated. Omitted on response blocks the engine treats as wholly translatable."
    • changedInput schema / properties / text / items / required
      Previous value: -[
      -  "text",
      -  "translatable"
      -]New value: +[
      +  "text"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "items": {
      +      "description": "Translated text blocks, in the same order and structure as the input. Blocks marked translatable: false are preserved verbatim.",
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "text": {
      +            "description": "Text content of the block",
      +            "type": "string"
      +          },
      +          "translatable": {
      +            "description": "Whether the block should be translated. Omitted on response blocks the engine treats as wholly translatable.",
      +            "type": "boolean"
      +          }
      +        },
      +        "required": [
      +          "text"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "items"
      +  ],
      +  "type": "object"
      +}
  3. Changed8 schema fields changedv1.0.2
    • addedInput schema / properties / content_type
      Added value: +{
      +  "description": "Specifies the content type of the text. Autodetected if omitted.",
      +  "enum": [
      +    "text/plain",
      +    "text/html",
      +    "application/xliff+xml"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / glossaries
      Added value: +{
      +  "description": "Array of glossary IDs to apply during translation (max 10). IDs must match format: gls_* (e.g., ['gls_xyz123', 'gls_abc456']). Glossaries enforce specific terminology and terms.",
      +  "items": {
      +    "maxLength": 255,
      +    "minLength": 1,
      +    "pattern": "^gls_[a-zA-Z0-9_-]+$",
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • changedInput schema / properties / instructions / description
      Previous value: -"A list of instructions to adjust the network’s behavior regarding the output (e.g., 'Use a formal tone')."New value: +"Optional list of short localization directives to adjust translation output. Each instruction MUST be no more than 20 words. These are NOT free-form LLM prompts — they are expert localization directives about formality, tone, or domain-specific terminology. Only provide instructions when the content specifically requires them; omitting instructions for general content preserves higher translation quality. Do NOT combine contradictory instructions (e.g., formal and informal tone together). Examples: 'Translate formally', 'Use a creative and concise tone', 'Make translation gender-neutral', 'Mask any price with the [price] placeholder', 'Use quotation marks (« ») for quotations'."
    • addedInput schema / properties / no_trace
      Added value: +{
      +  "description": "Privacy flag. If set to true, the request content will not be stored or traced by Lara. Use for sensitive content.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / priority
      Added value: +{
      +  "description": "Translation priority. 'normal' for real-time translations, 'background' for batch processing with lower priority.",
      +  "enum": [
      +    "normal",
      +    "background"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / reasoning
      Added value: +{
      +  "description": "Enables Lara Think multi-step linguistic analysis. Can increase processing time up to 10x but may improve translation quality for complex texts.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / style
      Added value: +{
      +  "description": "Controls how the translation balances accuracy against natural readability. 'faithful' stays close to the source, 'fluid' prioritizes natural readability, 'creative' allows more freedom in the translation.",
      +  "enum": [
      +    "faithful",
      +    "fluid",
      +    "creative"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / timeout_in_millis
      Added value: +{
      +  "description": "Custom timeout for the translation request in milliseconds. Max: 300000ms (5 minutes). Useful for very long texts.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 300000,
      +  "type": "integer"
      +}
  4. Changed2 schema fields changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / adapt_to
      Added value: +{
      +  "description": "A list of translation memory IDs for adapting the translation.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare the generic profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description must carry the operational burden. It does disclose non-obvious call-pattern behavior: one language per call requiring repeated invocations, and a mandatory ID-resolution step before glossary use. It does not discuss tracing/storage implications (no_trace lives only in the schema) or that repeated identical calls create new translations.

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 the core purpose, then two clearly flagged IMPORTANT blocks for the highest-risk failure modes. Every sentence carries guidance, though the target-language constraint is duplicated nearly verbatim from the schema description, adding a little length without new information.

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?

For a 14-parameter tool with 100% schema coverage and an output schema, the description only needs to cover routing and workflow pitfalls, which it does (multi-language fan-out, glossary ID resolution, instructions discipline). Remaining parameters (style, priority, reasoning, timeout, no_trace, content_type) are fully documented in the schema and need no repetition.

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 100% (baseline 3), and the description adds real meaning on top: it explains when to use 'instructions' and that they must not be contradictory, and it explains the 'gls_*' ID requirement plus the list_glossaries resolution workflow for 'glossaries'. The 'target' single-code rule is restated from the schema, which is mildly redundant but harmless.

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+resource ('Translate text between languages using Lara Translate') and immediately scopes the capabilities (detection, context-aware translation, memories, glossaries). It is unmistakably distinct from siblings like detect_language, list_glossaries, or add_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?

Gives explicit when-to-use and when-not-to-use rules: only supply 'instructions' when tone/formality/terminology adjustments are needed, call once per target language for multi-language requests, and call list_glossaries first when the user names a glossary. It even specifies the fallback (tell the user rather than guess an ID).

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