Lara Translate MCP Server

export_glossary

Read-onlyIdempotent

Export a glossary from your Lara Translate account as CSV, choosing unidirectional or multidirectional format for use in other tools.

Instructions

Exports a glossary as CSV from your Lara Translate account. Supports unidirectional and multidirectional formats.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	The glossary ID (format: gls_*, e.g., 'gls_xyz123')
`source`	No	The source language code. Required when content_type is 'csv/table-uni'
`content_type`	Yes	The export format. 'csv/table-uni' for unidirectional (requires source parameter), 'csv/table-multi' for multidirectional

Output Schema

TableJSON Schema

Name	Required	Description	Default
`value`	Yes	The exported glossary content serialised as CSV

Schema Changelog

Changes observed during successful MCP inspections.

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": false,
+  "properties": {
+    "value": {
+      "description": "The exported glossary content serialised as CSV",
+      "type": "string"
+    }
+  },
+  "required": [
+    "value"
+  ],
+  "type": "object"
+}

Addedv1.0.2May 4, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's burden is lighter. It adds the unidirectional/multidirectional format dimension but does not state whether export triggers file generation, where output goes, or any size limits.

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, purpose front-loaded before the format detail, with no filler. Every clause carries information.

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?

The tool is simple, an output schema exists so return values need no explanation, and annotations carry the safety semantics. The one minor gap is that the conditional 'source required for csv/table-uni' rule is only in the schema, not the description, but that is adequately covered elsewhere.

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%, so the schema already documents id, source, and the content_type enum plus the conditional source requirement. The description's mention of uni/multidirectional formats merely restates the enum, adding no syntax or behavioral detail beyond the schema.

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 clear verb+resource ('exports a glossary') plus the output format ('as CSV') and account scope, which distinguishes it from get_glossary/list_glossaries. It does not name or contrast with those siblings explicitly, so it stops short of a 5.

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?

There is no when-to-use guidance, no mention of prerequisites, and no alternatives such as get_glossary or list_glossaries. The only hint is that two export formats exist, which is format information rather than usage direction.

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