Skip to main content
Glama

bluente_translate_file

Start or cancel translation for uploaded files while preserving formatting, supporting multiple languages and translation engines.

Instructions

Start or cancel translation for an uploaded file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
actionNostart
fromNo
toNo
engineNoLLM
glossaryNo
custom_glossaryNo
bilingualNoline
vertical_bilingualNo
scannedNo
namespaceNo
metadataNo

Implementation Reference

  • The handler function for the `bluente_translate_file` tool, executing `client.translateFile`.
    async (args) =>
      executeTool(TOOL_NAME, async () => {
        if (args.action === "start" && (!args.from || !args.to)) {
          throw new BluenteApiError("Fields 'from' and 'to' are required when action is 'start'.");
        }
    
        return client.translateFile({
          id: args.id,
          action: args.action,
          from: args.from,
          to: args.to,
          engine: args.engine,
          glossary: args.glossary,
          customGlossary: args.custom_glossary,
          bilingual: args.bilingual,
          verticalBilingual: args.vertical_bilingual,
          scanned: args.scanned,
          namespace: args.namespace,
          metadata: args.metadata
        });
      })
  • Registration function for the `bluente_translate_file` tool.
    export function registerTranslateFileTool(server, { client }) {
      server.tool(
        TOOL_NAME,
        "Start or cancel translation for an uploaded file.",
        translateFileSchema,
        async (args) =>
          executeTool(TOOL_NAME, async () => {
            if (args.action === "start" && (!args.from || !args.to)) {
              throw new BluenteApiError("Fields 'from' and 'to' are required when action is 'start'.");
            }
    
            return client.translateFile({
              id: args.id,
              action: args.action,
              from: args.from,
              to: args.to,
              engine: args.engine,
              glossary: args.glossary,
              customGlossary: args.custom_glossary,
              bilingual: args.bilingual,
              verticalBilingual: args.vertical_bilingual,
              scanned: args.scanned,
              namespace: args.namespace,
              metadata: args.metadata
            });
          })
      );
    }
  • Zod schema definition for input validation of `bluente_translate_file`.
    export const translateFileSchema = {
      id: z.string().min(1),
      action: z.enum(["start", "cancel"]).default("start"),
      from: z.string().min(2).optional(),
      to: z.string().min(2).optional(),
      engine: engineSchema,
      glossary: binaryFlagSchema.default(0),
      custom_glossary: binaryFlagSchema.default(0),
      bilingual: z.enum(["line", "paragraph", "none"]).default("line"),
      vertical_bilingual: binaryFlagSchema.default(0),
      scanned: binaryFlagSchema.default(0),
      namespace: z.string().optional(),
      metadata: z.record(z.any()).optional()
    };
Behavior2/5

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

No annotations provided, so description carries full burden of behavioral disclosure. Fails to indicate this is likely an asynchronous operation (evidenced by the status-checking sibling), doesn't explain side effects of 'cancel' (whether it stops processing or deletes results), or mention engine behavior differences (GTC vs LLM vs PPE).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is front-loaded and contains no wasted words. However, it is inappropriately concise given the high parameter complexity (12 params, nested objects, multiple enums) and lack of schema documentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a complex 12-parameter tool with nested objects and no output schema. Missing explanation of engine options (GTC/LLM/PPE), bilingual formatting modes, glossary behavior, and return value structure. The presence of 'bluente_get_translation_status' as a sibling strongly implies async behavior that should be documented here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage across 12 parameters. The description only implicitly covers the 'action' parameter via 'Start or cancel', leaving 11 parameters (languages, engine selection, glossary flags, bilingual formatting, namespace, metadata) completely undocumented. Insufficient compensation for the schema documentation gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the core action (start/cancel) and resource (translation for uploaded file), but fails to differentiate from sibling 'bluente_translate_document_workflow'. The phrase 'uploaded file' implies prerequisite use of upload_file, but doesn't clarify why this tool exists alongside a workflow alternative.

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?

Provides no explicit guidance on when to use this versus 'bluente_translate_document_workflow', nor when to choose 'cancel' versus 'start'. Missing critical async workflow guidance (e.g., that 'bluente_get_translation_status' should be used to poll for completion), despite the existence of the status-checking sibling.

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