Skip to main content
Glama

下载译文

fanbei_download
Read-only

Get a 10-minute download link for a completed document translation and optionally save the file to a local directory, returning its saved path.

Instructions

取成品的下载链接(10 分钟有效)。save_to 给本地目录时,stdio 模式下会直接把文件写盘并返回路径。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tran_id": "<tran_id>"
    },
    "name": "fanbei_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
save_toNo
tran_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the link expires in 10 minutes, and when save_to points to a local directory in stdio mode the file is written to disk and the path is returned. That is valuable operational context. There is mild tension with readOnlyHint=true since a local file write modifies the environment, though the remote operation is a read; I treat this as disclosure rather than contradiction.

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?

Two compact clauses with the expiry constraint front-loaded and no filler. It is efficient, though the dense parenthetical phrasing and missing explicit default-behavior statement leave it slightly under-specified rather than merely concise.

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?

With no output schema and a mutation-adjacent file-write path, the description should say more: what a failure looks like when the artifact is not ready, how save_to behaves in non-stdio/remote mode, and what the returned link or path looks like. It covers expiry and the stdio write but leaves these gaps.

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?

Schema coverage is 0%, so the description must carry parameter meaning. It explains save_to well (local directory, triggers a disk write in stdio mode) but says nothing about tran_id beyond the required flag, nor what the default empty save_to produces (presumably link only).

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?

A specific verb and resource are present: retrieve a download link for a finished product ('取成品的下载链接'). An agent can tell this fetches output rather than status or listing. It does not distinguish itself from siblings such as fanbei_task_status or fanbei_list_tasks, so it stops short of a 5.

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?

Usage is only implied: you call it to get the artifact, presumably after a translation task finishes. The description never states the prerequisite (task must be complete), what happens if the task is still running, or why to choose this over fanbei_task_status.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.