Lara Translate MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LARA_ACCESS_KEY_ID | Yes | Your Lara API access key ID | |
| LARA_ACCESS_KEY_SECRET | Yes | Your Lara API access key secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| translateB | Translate text between languages with support for language detection and context-aware translations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. An agent can unambiguously select the sole translation operation.
With a single tool named 'translate', there are no competing naming conventions or inconsistencies. The name is clear and directly reflects its purpose.
One tool is borderline thin for a translation server; while it may cover the core operation, a single tool leaves little room for auxiliary operations like listing languages or batch translation. The count is minimal but not egregiously mismatched.
The core translation operation is present and includes language detection and context-aware translation, covering the primary workflow. Minor gaps such as language enumeration or batch translation exist but can likely be worked around by agents.