bluente-translate
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BLUENTE_API_KEY | Yes | Your Bluente API key | |
| BLUENTE_API_BASE_URL | No | The base URL for the Bluente API | https://api.bluente.com/api/20250924 |
| BLUENTE_API_TIMEOUT_MS | No | Timeout for API requests in milliseconds | 90000 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bluente_get_supported_languagesA | List all language pairs currently supported by the Bluente translation platform. |
| bluente_upload_fileB | Upload a source document to Bluente and get a translation task id. |
| bluente_get_translation_statusA | Query a task status by id. Use this to poll progress after starting translation. |
| bluente_translate_fileC | Start or cancel translation for an uploaded file. |
| bluente_download_fileC | Download the translated file once the task status is READY. |
| bluente_translate_document_workflowB | Run end-to-end translation: upload, start, poll until READY, and optionally download. |
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 6 tools
The tools have mostly distinct purposes with clear boundaries: upload, start/cancel translation, check status, download, list languages, and a workflow wrapper. The only potential overlap is between bluente_translate_document_workflow (end-to-end) and the individual upload/translate/status/download tools, but their descriptions clarify this as a convenience wrapper versus granular control.
All tools follow a consistent bluente_verb_noun pattern with snake_case throughout. The naming is predictable and aligned with the server's domain, making it easy for agents to understand the function of each tool at a glance.
With 6 tools, this server is well-scoped for document translation workflows. It covers the essential steps (upload, translate, status, download, languages) plus a workflow helper, avoiding bloat while providing complete coverage for the domain.
The toolset provides complete coverage for document translation: upload source, start/cancel translation, poll status, download result, list supported languages, and an end-to-end workflow. There are no obvious gaps; agents can handle both granular and automated translation tasks effectively.