Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

import_tmx

Import a TMX file into a translation memory. Returns an import job ID to check status until complete.

Instructions

Imports a TMX file into a translation memory. This is an async operation that returns an import job object containing an import_id. Poll with check_import_status using the returned import_id until the import is complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the memory to update. Format: mem_xyz123.
tmx_contentYesThe content of the tmx file to upload.

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)
Behavior4/5

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

Discloses async operation and return structure. Annotations already indicate readOnlyHint=false and destructiveHint=false; description adds valuable context about polling and job object.

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?

Two concise sentences front-loading purpose and usage. No waste.

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 existence (returning import job with import_id) and sibling tools for polling, description is complete and sufficient for effective use.

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 descriptions for both parameters. Description adds no extra semantics beyond schema, so baseline 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 verb (imports), resource (TMX file into translation memory), and async behavior. It distinguishes from siblings like import_glossary_csv and check_import_status.

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?

Provides explicit guideline to poll with check_import_status using the returned import_id. Does not explicitly say when not to use, but context from sibling tools implies alternatives.

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