Skip to main content
Glama

bluente_download_file

Download translated documents in PDF, DOCX, or XLSX format after translation is complete. Retrieve files with original formatting preserved from the Bluente Translate service.

Instructions

Download the translated file once the task status is READY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
to_typeNodocx
output_pathNo

Implementation Reference

  • Handler function and tool registration for 'bluente_download_file'. It uses the provided client to perform the download.
    export function registerDownloadFileTool(server, { client }) {
      server.tool(
        TOOL_NAME,
        "Download the translated file once the task status is READY.",
        downloadFileSchema,
        async ({ id, to_type: toType, output_path: outputPath }) =>
          executeTool(TOOL_NAME, async () => client.downloadFile({ id, toType, outputPath }))
      );
  • Input schema validation for 'bluente_download_file' tool.
    export const downloadFileSchema = {
      id: z.string().min(1),
      to_type: z.enum(["pdf", "docx", "xlsx"]).default("docx"),
      output_path: z.string().optional()
    };
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. Only behavioral trait mentioned is the READY status prerequisite. Missing: error handling when not ready, whether output is returned as content or saved to disk (relevant given 'output_path' parameter), and side effects.

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, front-loaded with action. Efficiently structured but arguably undersized given the complete lack of schema documentation and annotations—it sacrifices necessary detail for brevity.

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?

With 3 undocumented parameters, no output schema, and no annotations, the description leaves critical gaps. While the READY state reference is helpful workflow context, the agent lacks guidance on parameter semantics, return format, and filesystem side effects.

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 coverage is 0%, requiring heavy description compensation. The text implies 'id' refers to a task ID (via 'task status' reference) but fails to explain 'output_path' (filesystem write location?) or 'to_type' (format conversion options). Only minimal implicit guidance for one of three parameters.

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?

Clear verb ('Download') and resource ('translated file') with specific workflow context ('once the task status is READY'). The READY condition effectively distinguishes this from sibling upload/translate tools by implying it's the final retrieval step in a workflow sequence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides conditional guidance via 'once the task status is READY', implying prerequisites. However, it doesn't explicitly name the sibling status-checking tool (bluente_get_translation_status) or describe error behavior if called prematurely.

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