Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

add_translation

Add a translation to your memory by specifying source and target languages, the sentence and its translation. Optionally include context sentences to improve future translation accuracy.

Instructions

Adds a translation to a translation memory in your Lara Translate account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID or list of IDs where to save the translation unit. Format: mem_xyz123
sourceYesThe source language code of the sentence, it MUST be a language supported by the system, use the list_languages tool to get a list of all the supported languages
targetYesThe target language code of the translation, it MUST be a language supported by the system, use the list_languages tool to get a list of all the supported languages
sentenceYesThe source sentence
translationYesThe translated sentence
tuidNoTranslation Unit unique identifier
sentence_beforeNoThe sentence before the source sentence to specify the context of the translation unit
sentence_afterNoThe sentence after the source sentence to specify the context of the translation unit

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesImport job identifier
beginNoBegin offset of the import
endNoEnd offset of the import
channelNoChannel identifier used by the import
sizeNoTotal number of units in the import
progressNoImport progress between 0 and 1 (1 means complete)
Behavior2/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description merely restates that it adds a translation, adding no additional behavioral context such as side effects, limits, or duplicate handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no superfluous words, efficiently conveying the tool's purpose.

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?

While the schema covers parameters and an output schema exists, the description lacks context about translation memories, the role of optional parameters (tuid, sentence_before, sentence_after), and prerequisites. It is adequate but not comprehensive.

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 100%, with all 8 parameters well-documented in the schema. The description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

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 action (adds), resource (translation to translation memory), and context (Lara Translate account), effectively distinguishing it from sibling tools like add_glossary_entry or delete_translation.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as translate or add_glossary_entry. There are no prerequisites, exclusions, or usage scenarios mentioned.

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/translated/lara-mcp'

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