Skip to main content
Glama
translated

Lara Translate MCP Server

by translated

add_glossary_entry

Add or replace a term entry in a Lara Translate glossary, supporting monodirectional and multidirectional glossaries.

Instructions

Adds or replaces an entry in a glossary in your Lara Translate account. Supports both monodirectional and multidirectional glossaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe glossary ID (format: gls_*, e.g., 'gls_xyz123')
termsYesArray of terms with language and value. For monodirectional glossaries, the first term is the source and the rest are targets. For multidirectional glossaries, all terms are treated equally. Use the list_languages tool to get supported language codes.
guidNoOptional entry identifier. Use this for multidirectional glossaries or to update a specific entry.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesImport job identifier
beginNoBegin offset of the import
endNoEnd offset of the import
channelNoChannel identifier used by the import
sizeNoTotal number of entries in the import
progressNoImport progress between 0 and 1 (1 means complete)
Behavior3/5

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

Annotations already indicate mutation (readOnlyHint false) and non-destructiveness. The description adds that it handles both glossary directions, but lacks details on conflict resolution or idempotency, offering minimal extra behavioral context.

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, no redundant information, front-loaded with key action. Every word earns its place.

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 details are omitted appropriately. The description covers core behavior and parameter nuances, but misses usage guidelines. Overall sufficiently complete for a moderate-complexity tool.

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%, but the description adds meaning by explaining term ordering for monodirectional vs multidirectional glossaries and referencing list_languages, which goes beyond the schema's field descriptions.

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?

The description clearly states the tool adds or replaces a glossary entry, and distinguishes from siblings by mentioning support for both monodirectional and multidirectional glossaries, which sets it apart from delete_glossary_entry or create_glossary.

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?

The description provides no guidance on when to use this tool versus alternatives like add_translation or create_glossary. It only notes glossary type support, leaving usage context ambiguous.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/translated/lara-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server