Lara Translate MCP Server

list_glossaries

Read-onlyIdempotent

Retrieve all glossaries in your Lara Translate account to review term collections that enforce specific terminology during translation.

Instructions

Lists all glossaries in your Lara Translate account. Glossaries are collections of terms with their translations that enforce specific terminology during translation.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`items`	Yes	Glossaries accessible to the authenticated account

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.1.0Oct 15, 2026
- addedOutput schema / properties / items / items / properties / isPersonal / anyOf
```
Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / isPersonal / type
```
Removed value: -[
-  "boolean",
-  "null"
-]
```
- addedOutput schema / properties / items / items / properties / ownerId / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / ownerId / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
Changed10 schema fields changedv2.0.1Oct 13, 2026
- addedOutput schema / properties / items / items / properties / createdAt / anyOf
```
Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / createdAt / description
```
Removed value: -"ISO 8601 timestamp"
```
- removedOutput schema / properties / items / items / properties / createdAt / type
```
Removed value: -"string"
```
- changedOutput schema / properties / items / items / 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 / items / items / properties / isPersonal / type
```
Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]
```
- changedOutput schema / properties / items / items / properties / ownerId / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / items / items / properties / updatedAt / anyOf
```
Added value: +[
+  {
+    "description": "ISO 8601 timestamp",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / items / items / properties / updatedAt / description
```
Removed value: -"ISO 8601 timestamp"
```
- removedOutput schema / properties / items / items / properties / updatedAt / type
```
Removed value: -"string"
```
- changedOutput schema / properties / items / items / required
```
Previous value: -[
-  "id",
-  "name",
-  "ownerId",
-  "createdAt",
-  "updatedAt",
-  "isPersonal"
-]New value: +[
+  "id",
+  "name"
+]
```
Changed1 schema field changedv2.0.0Sep 29, 2026
- removedOutput schema / properties / items / items / 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": false,
+  "properties": {
+    "items": {
+      "description": "Glossaries accessible to the authenticated account",
+      "items": {
+        "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"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

Addedv1.0.2May 4, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and idempotency profile is fully covered. The description adds only the domain meaning of a glossary, not additional behavioral detail such as result ordering or size.

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 sentences, both earning their place: the first states the action and scope, the second supplies the domain definition needed to interpret results. Front-loaded with the action and free of filler.

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, the description needn't explain return values, and annotations cover the safety profile. The only residual gap is the absence of guidance distinguishing listing all glossaries from the count or single-glossary siblings.

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?

The tool takes zero parameters, so there are no parameter semantics to document; the baseline for a parameterless tool is 4. Schema coverage is 100% and the empty object schema is unambiguous.

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 ('Lists') and resource ('all glossaries'), and the phrase 'all glossaries' implicitly distinguishes it from the singular get_glossary sibling. It also defines what a glossary is, which is useful domain context, but it doesn't explicitly name the sibling it contrasts with.

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?

Usage is implied by the word 'Lists all' – an agent can infer this is the enumeration tool versus get_glossary for a single glossary. However, there is no explicit when-to-use statement, no mention of the get_glossary alternative, and no note about when listing is preferable to fetching counts.

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