Skip to main content
Glama
Sign In
Fanbei

Fanbei

by ee58594
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

查询任务进度

fanbei_task_status
Read-only

Check a single translation task by tran ID to view its status, progress percentage, and sub-file details; status 3 confirms translation is complete and ready to download.

Instructions

按 tranId 查单个任务的状态、进度百分比与子文件明细。status=3 表示翻译完成、可以下载。

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_task_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
tran_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the returned fields (status, progress %, sub-file details) and decoding status=3 as completion, which matters because there is no output schema.

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 short sentences, front-loaded with what is returned and followed by the one status code that changes agent behavior. Nothing is wasted.

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?

For a simple read-only single-lookup tool with one parameter and no output schema, the description covers return contents and a key status semantic. The only gap is not indicating where a valid tran_id is obtained.

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 description coverage is 0% for the single required parameter, so the description carries the burden. It says lookup is 按 tranId, but does not explain the ID's origin (e.g., returned by fanbei_translate_document) or format, so it adds only marginal meaning over the schema property name.

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?

States a specific verb+resource: query a single task's status, progress percentage, and sub-file details by tranId. The word 单个 (single) implicitly separates it from the list-all sibling fanbei_list_tasks, though no sibling is named explicitly.

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?

Implies usage: look up one task when you already have its tranId. The note that status=3 means the translation is finished and downloadable hints that fanbei_download is the follow-up, but it never states when to prefer this over fanbei_list_tasks or where the tranId comes from.

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

Deploy Server

Other Tools