Skip to main content
Glama
Sign In
Lara Translate MCP Server

Lara Translate MCP Server

by translated
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_glossary

DestructiveIdempotent

Rename a glossary in your Lara Translate account. Supply the glossary ID and the new name.

Instructions

Updates the name of a glossary in your Lara Translate account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>",
      "name": "<name>"
    },
    "name": "update_glossary"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe glossary ID (format: gls_*, e.g., 'gls_xyz123')
nameYesThe new name for the glossary

Output Schema

NameRequiredDescriptionDefault
idYesUnique glossary identifier (format: gls_*)
nameYesDisplay name of the glossary
ownerIdNoIdentifier of the glossary owner
createdAtNo
updatedAtNo
isPersonalNoTrue 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.

  1. Changed4 schema fields changedv2.1.0
    • 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"
-]
  2. Changed10 schema fields changedv2.0.1
    • 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"
+]
  3. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / name / description
      Added value: +"The new name for the glossary"
    • addedInput schema / properties / name / maxLength
      Added value: +250
    • removedOutput schema / additionalProperties
      Removed value: -{}
  4. Changed1 schema field changedv1.0.4
    • 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"
+}
  5. Addedv1.0.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered structurally. The description contributes one extra fact beyond that: the mutation is limited to the name field, implying other glossary settings are untouched. It adds nothing about reversibility of the old name or required permissions.

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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification rather than maximal conciseness.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the 2-param schema is fully documented. For a simple rename tool this is minimally viable, but it omits the natural-rename caveat (whether the new name must be unique) and any routing versus the other glossary mutators.

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% (both 'id' and 'name' are documented with pattern and length constraints), so the schema carries the parameter burden. The description's phrase 'the name of a glossary' loosely maps to the 'name' param but adds no format or constraint information beyond it.

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 ('Updates') plus resource ('the name of a glossary'), and the scope is narrowed to the name field, which separates it from create_glossary/delete_glossary. It stops short of explicitly naming any sibling or stating what it does not modify, so it is clear but not sibling-differentiating.

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 guidance on when to use this versus create_glossary or delete_glossary, no prerequisites (e.g. ownership/permissions), and no exclusions. Usage must be inferred entirely from the verb and the sibling list.

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

Deploy Server

Other Tools