Lara Translate MCP Server

create_glossary

Create a named glossary in your Lara Translate account to enforce specific terminology during translation.

Instructions

Create a glossary with a custom name in your Lara Translate account. Glossaries enforce specific terminology during translation.

Input Schema

Name	Required	Description	Default
`name`	Yes	The name of the new glossary, it should be short and descriptive, like 'brand_terms' or 'legal_terminology'

Output Schema

Name	Required	Description
`id`	Yes	Unique glossary identifier (format: gls_*)
`name`	Yes	Display name of the glossary
`ownerId`	No	Identifier of the glossary owner
`createdAt`	No
`updatedAt`	No
`isPersonal`	No	True if the glossary is private to the owner. Omitted for some account types (e.g. team plans).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.0Oct 15, 2026

addedOutput schema / properties / isPersonal / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / isPersonal / type
```
Removed value: -[
-  "boolean",
-  "null"
-]
```

addedOutput schema / properties / ownerId / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / ownerId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed10 schema fields changedv2.0.1Oct 13, 2026

addedOutput schema / properties / createdAt / anyOf

Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / createdAt / description
```
Removed value: -"ISO 8601 timestamp"
```
removedOutput schema / properties / createdAt / type
```
Removed value: -"string"
```

changedOutput schema / properties / isPersonal / description

Previous value: -"True if the glossary is private to the owner"New value: +"True if the glossary is private to the owner. Omitted for some account types (e.g. team plans)."

changedOutput schema / properties / isPersonal / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

changedOutput schema / properties / ownerId / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

addedOutput schema / properties / updatedAt / anyOf

Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / updatedAt / description
```
Removed value: -"ISO 8601 timestamp"
```
removedOutput schema / properties / updatedAt / type
```
Removed value: -"string"
```

changedOutput schema / required

Previous value: -[
-  "id",
-  "name",
-  "ownerId",
-  "createdAt",
-  "updatedAt",
-  "isPersonal"
-]New value: +[
+  "id",
+  "name"
+]

Changed3 schema fields changedv2.0.0Sep 29, 2026
- addedInput schema / properties / name / description
```
Added value: +"The name of the new glossary, it should be short and descriptive, like 'brand_terms' or 'legal_terminology'"
```
- addedInput schema / properties / name / maxLength
```
Added value: +250
```
- 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": {
+    "createdAt": {
+      "description": "ISO 8601 timestamp",
+      "type": "string"
+    },
+    "id": {
+      "description": "Unique glossary identifier (format: gls_*)",
+      "type": "string"
+    },
+    "isPersonal": {
+      "description": "True if the glossary is private to the owner",
+      "type": "boolean"
+    },
+    "name": {
+      "description": "Display name of the glossary",
+      "type": "string"
+    },
+    "ownerId": {
+      "description": "Identifier of the glossary owner",
+      "type": "string"
+    },
+    "updatedAt": {
+      "description": "ISO 8601 timestamp",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name",
+    "ownerId",
+    "createdAt",
+    "updatedAt",
+    "isPersonal"
+  ],
+  "type": "object"
+}

Addedv1.0.2May 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, and openWorld=false, so the safety profile is covered. The description adds useful context that the glossary lives in the user's Lara Translate account and affects translation behavior, but says nothing about duplicate-name handling, permissions, or side effects beyond what annotations provide.

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 short sentences with zero filler; the action is front-loaded and the explanatory clause about terminology follows efficiently.

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 an output schema present, return values need not be explained, and a one-parameter create tool with full schema coverage is nearly complete. It could still mention that the new glossary starts empty and requires add_glossary_entry, but nothing essential to invoking the tool 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% and the single 'name' parameter is well documented in the schema (maxLength 250, examples like 'brand_terms'). The description adds no parameter-level detail beyond the schema, so baseline 3 applies.

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+resource ('Create a glossary') and adds what a glossary is for ('enforce specific terminology during translation'). It does not explicitly differentiate itself from siblings like list_glossaries or add_glossary_entry, though the create/list/get/update/delete naming pattern makes the intent inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implied usage only: the description explains why glossaries exist (terminology enforcement), which hints at when to create one, but gives no explicit guidance on when to create a new glossary versus using an existing one, and no mention of the follow-up step (adding entries).

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