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 misselection between tools. Its purpose—translating text between languages—is unambiguous.
The single tool uses a clear imperative verb name ('translate') with no competing conventions to clash with. Trivially consistent by construction.
One tool is a very thin surface for a translation server, even if the core operation is well chosen. It sits in the borderline '1-2 tools feels thin' band rather than an extreme mismatch.
Core translation is covered, but there are notable gaps: no tool to list or discover supported languages, no batch/multi-segment translation, and no document or glossary handling. Agents can work around these but may hit dead ends when they need language metadata.