Skip to main content
Glama
Sign In
Fanbei

Fanbei

by ee58594
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

翻译报价

fanbei_quote
Read-only

Estimates credit usage by page count and translation options, then checks whether your balance is sufficient before placing an order.

Instructions

按页数与选项估算积分消耗，并检查余额是否够用。下单前先报个价。

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": {
      "pages": "<pages>"
    },
    "name": "fanbei_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocrNo
pagesYes
engineNoBAIDU
bilingualNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful context that this is a pre-order cost estimate that also verifies balance, but it says nothing about what the estimate contains, whether it reserves credits, or how stale a quote becomes.

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-loading the cost-estimation purpose and closing with the timing cue. No wasted wording.

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?

For a read-only quoting tool with no output schema, the description explains the intent but not the result shape (cost figure, balance, shortfall) nor the meaning of three of four inputs. Adequate to recognize the tool, not fully adequate to invoke it confidently with non-default options.

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 description coverage is 0% across four parameters. The description only gestures at '按页数与选项', covering the required pages field vaguely, and leaves engine (default BAIDU), ocr, and bilingual completely unexplained — an agent cannot tell what values are legal or what these options cost.

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 concrete verb+resource: estimates credit consumption from page count and options, and verifies balance sufficiency. This clearly separates it from fanbei_translate_document (which actually places the order), though it never names that sibling explicitly.

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?

'下单前先报个价' gives a clear trigger point: call this before submitting a translation order. It does not enumerate exclusions or name which sibling to call afterwards, so the alternative routing is only implied.

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