Skip to main content
Glama
Bluente

bluente-translate

Official
by Bluente
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

bluente_upload_file

Upload documents for translation while preserving formatting. Choose translation engines and glossary options to process files.

Instructions

Upload a source document to Bluente and get a translation task id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesAbsolute or relative path to source file.
engineNoTranslation engine option.LLM
glossaryNoEnable glossary matching: 0 or 1.

Implementation Reference

  • src/tools/upload-file.tool.js:6-13 (handler)
    The handler for `bluente_upload_file`, which utilizes the client's `uploadFile` method.
    export function registerUploadFileTool(server, { client }) {
  server.tool(
    TOOL_NAME,
    "Upload a source document to Bluente and get a translation task id.",
    uploadFileSchema,
    async ({ file_path: filePath, engine, glossary }) =>
      executeTool(TOOL_NAME, async () => client.uploadFile({ filePath, engine, glossary }))
  );
  • src/tools/schemas.js:6-10 (schema)
    Zod schema definition for `bluente_upload_file` tool inputs.
    export const uploadFileSchema = {
  file_path: z.string().min(1).describe("Absolute or relative path to source file."),
  engine: engineSchema.describe("Translation engine option."),
  glossary: binaryFlagSchema.default(0).describe("Enable glossary matching: 0 or 1.")
};
  • src/tools/upload-file.tool.js:6-14 (registration)
    Registration function for `bluente_upload_file`.
    export function registerUploadFileTool(server, { client }) {
  server.tool(
    TOOL_NAME,
    "Upload a source document to Bluente and get a translation task id.",
    uploadFileSchema,
    async ({ file_path: filePath, engine, glossary }) =>
      executeTool(TOOL_NAME, async () => client.uploadFile({ filePath, engine, glossary }))
  );
}

Tool Definition Quality

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the return value (translation task id) which is critical since there's no output schema, and implies state mutation via 'upload'. However, it omits idempotency, side effects (e.g., storage persistence), error behaviors, or whether the translation starts automatically.

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?

Single, front-loaded sentence of 11 words with zero redundancy. Every word earns its place by stating the action, target, and return value immediately.

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?

Given the lack of output schema, the description adequately covers the return value (translation task id). With 100% schema parameter coverage and no complex nested objects, the description provides sufficient context for a 3-parameter upload tool, though it could mention this is the first step in an async workflow.

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?

Input schema has 100% description coverage, establishing a baseline of 3. The description doesn't add semantic context beyond the schema (e.g., doesn't explain what GTC/LLM/PPE engines mean, or when to enable glossary matching), but doesn't need to given the schema completeness.

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?

The description clearly states the verb (upload), resource (source document to Bluente), and specific outcome (get a translation task id). However, it doesn't explicitly differentiate from sibling 'bluente_translate_file' or clarify if this initiates an async workflow versus other translation methods.

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?

No guidance provided on when to use this tool versus alternatives like 'bluente_translate_file' or 'bluente_translate_document_workflow'. Doesn't indicate that the returned task id should be used with 'bluente_get_translation_status' or prerequisites like file format requirements.

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/Bluente/bluente-translate'

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