Lara Translate MCP Server

check_import_status

Read-onlyIdempotent

Check the status of a TMX import job. Poll with the import ID until complete; the response includes a progress field.

Instructions

Checks the status of a TMX import job started by import_tmx. Poll this tool with the import_id returned from import_tmx until the import is complete. The response includes a progress field to track completion.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The ID of the import job

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: this is a polling endpoint, the ID originates from import_tmx's response, and progress is the field to watch for completion.

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?

Three short sentences, front-loaded with the purpose and followed by the polling instruction and completion signal. The progress-field sentence is somewhat redundant with the existing output schema, but overall there is little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With rich annotations, a fully described single-param schema, and an output schema carrying the return values, the description needs only to explain pairing and polling — which it does. The only missing piece is explicit disambiguation from check_glossary_import_status.

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% with a single parameter, so the baseline would be 3. The description earns an extra point by disclosing provenance — the id is the value returned by import_tmx — which the schema's generic "The ID of the import job" does not convey; a minor naming drift ("import_id" vs schema's "id") is the only friction.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Checks the status of a TMX import job") and names the tool that creates the job (import_tmx), which implicitly separates it from the look-alike sibling check_glossary_import_status. It is clear and scoped, though it never explicitly rules out the glossary-status sibling.

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?

Gives concrete operational guidance: poll this tool with the import_id returned from import_tmx until the import is complete. That is a clear when-to-use trigger and an exit condition. It stops short of naming the alternative (check_glossary_import_status) for non-TMX imports.

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