Lara Translate MCP Server

import_tmx

Destructive

Imports a TMX file into a translation memory, returning an async import job ID. Poll check_import_status until the import completes.

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

Name	Required	Description	Default
`id`	Yes	The ID of the memory to update. Format: mem_xyz123.
`tmx_content`	Yes	The content of the tmx file to upload.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Import job identifier
`end`	No	End offset of the import
`size`	No	Total number of units in the import
`begin`	No	Begin offset of the import
`channel`	No	Channel identifier used by the import
`progress`	No	Import progress between 0 and 1 (1 means complete)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.0.0Sep 29, 2026
- removedOutput schema / additionalProperties
```
Removed value: -{}
```

Changed1 schema field changedv1.0.4May 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "begin": {
+      "description": "Begin offset of the import",
+      "type": "number"
+    },
+    "channel": {
+      "description": "Channel identifier used by the import",
+      "type": "number"
+    },
+    "end": {
+      "description": "End offset of the import",
+      "type": "number"
+    },
+    "id": {
+      "description": "Import job identifier",
+      "type": "string"
+    },
+    "progress": {
+      "description": "Import progress between 0 and 1 (1 means complete)",
+      "type": "number"
+    },
+    "size": {
+      "description": "Total number of units in the import",
+      "type": "number"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}

Addedv1.0.0Jan 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotent, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the operation is asynchronous and returns an import job with an import_id that must be polled. It does not explain what 'destructive' means here (e.g., whether existing translation units are merged or overwritten), leaving a small gap.

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?

Three short sentences, front-loaded with what the tool does, then the async contract, then the follow-up action. Every sentence carries information the agent needs; nothing is redundant.

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?

An output schema exists, so the return shape needn't be explained, yet the description still highlights the import_id field that drives the polling loop. For a 2-param destructive async tool, the description covers the operation, its async nature, and the required next step — nothing material is missing.

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 description coverage is 100% — both 'id' (with mem_xyz123 format) and 'tmx_content' are documented in the schema itself. The description adds no parameter-level detail beyond what the schema provides, so the baseline 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?

States a specific verb+resource ('Imports a TMX file into a translation memory') and names the exact file format, which cleanly separates it from the sibling import_glossary_csv. An agent can identify the operation without opening the schema.

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?

Explicitly tells the agent this is async and to poll with check_import_status using the returned import_id, which is the key usage context for a sibling that exists in the tool list. It does not state when-not to use it or how it differs from other memory-writing tools like add_translation, so it stops short of full when/alternative guidance.

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