Lara Translate MCP Server

check_glossary_import_status

Read-onlyIdempotent

Check the status of a glossary CSV import job. Poll with the import ID returned by import_glossary_csv until the import is complete.

Instructions

Checks the status of a glossary CSV import job started by import_glossary_csv. Poll this tool with the import_id returned from import_glossary_csv until the import is complete.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The ID of the glossary 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 entries 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 entries in the import",
+      "type": "number"
+    }
+  },
+  "required": [
+    "id"
+  ],
+  "type": "object"
+}

Addedv1.0.2May 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds the non-obvious operational trait that this is a polling endpoint to be called repeatedly until completion, which is genuine context beyond the annotations, though it says nothing about rate limits or what a terminal state looks like.

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 tight sentences, front-loaded with the purpose and followed immediately by the actionable polling instruction. Nothing wasted.

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 single-parameter polling tool with an output schema and full annotation coverage, everything an agent needs is present: what it does, when to call it, and how to drive the poll loop. Return-value details are appropriately left to the output schema.

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%, so baseline is 3. The description adds provenance the schema lacks — the id comes from import_glossary_csv — which helps the agent source the value, though it calls it 'import_id' while the schema names it 'id', a minor mismatch.

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?

Specific verb ('checks the status') plus resource ('glossary CSV import job'), and it names the originating sibling tool import_glossary_csv, which distinguishes it from the TMX-oriented check_import_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?

Explicitly states when to call it (after import_glossary_csv) and how (poll with the returned import_id until complete). It does not, however, explicitly rule out or contrast with the sibling check_import_status, leaving that routing to inference.

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