Skip to main content
Glama

bluente_get_translation_status

Check the progress of a document translation task by its ID. Use this to monitor status after initiating translation through the bluente-translate server.

Instructions

Query a task status by id. Use this to poll progress after starting translation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTask id returned by upload endpoint.
entryNopdf

Implementation Reference

  • This is the MCP tool handler definition for `bluente_get_translation_status`. It uses the provided `client` to invoke the `getTranslationStatus` method.
    server.tool(
      TOOL_NAME,
      "Query a task status by id. Use this to poll progress after starting translation.",
      getStatusSchema,
      async ({ id, entry }) => executeTool(TOOL_NAME, async () => client.getTranslationStatus({ id, entry }))
    );
  • Tool registration function for the `bluente_get_translation_status` tool.
    export function registerGetTranslationStatusTool(server, { client }) {
      server.tool(
        TOOL_NAME,
        "Query a task status by id. Use this to poll progress after starting translation.",
        getStatusSchema,
        async ({ id, entry }) => executeTool(TOOL_NAME, async () => client.getTranslationStatus({ id, entry }))
      );
    }
  • The underlying client method that performs the API call to fetch translation status.
    async getTranslationStatus({ id, entry }) {
      return this.requestJson(API_PATHS.GET_TRANSLATION_STATUS, {
        method: "GET",
        query: { id, entry }
      });
    }
Behavior3/5

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

No annotations provided, so description carries full burden. 'Poll progress' implies repeated safe reads, but description lacks explicit safety guarantees, rate limits, or return value structure. Adequate but minimal behavioral context.

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?

Two sentences, zero waste. Front-loaded with action ('Query') and immediate workflow context ('Use this to poll'). Every word earns its place.

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

Completeness3/5

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

Adequate for a simple 2-parameter polling tool, but gaps remain: the 'entry' parameter is unexplained, no output schema exists to document return values, and mutation safety is undescribed due to missing annotations.

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 50% (only 'id' is described; 'entry' lacks description). Description mentions 'by id' but fails to explain the undocumented 'entry' parameter (enum pdf/word), leaving its purpose and relationship to status querying unexplained.

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

Purpose5/5

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

Clear verb ('Query') and resource ('task status') with specific scope ('by id'). The phrase 'after starting translation' effectively distinguishes this polling tool from siblings like bluente_translate_file and bluente_upload_file.

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

Usage Guidelines4/5

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

Explicitly states when to use ('to poll progress after starting translation'), providing clear temporal workflow guidance. Lacks explicit 'when not to use' or named alternatives, but the context strongly implies it is not for initiating translations.

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