Skip to main content
Glama

可选翻译引擎

fanbei_engines
Read-only

Lists available translation engines with per-page credit costs and capability boundaries, and returns engine codes for configuring other translation tools.

Instructions

列出可用于翻译的引擎(模型档与传统网页引擎)、每页积分与能力边界。code 用于其它工具的 engine 参数。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fanbei_engines"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 meaningful non-structured context by disclosing what the listing contains — per-page credit costs and capability boundaries — which is not derivable from the empty schema. It omits any mention of auth requirements, though that is minor for a read-only listing.

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: the first states what is listed and what each entry carries, the second states the purpose of the returned code. Nothing is repetitive and the core purpose is front-loaded.

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?

With no parameters, no output schema and annotations already covering safety, this is close to complete — the agent knows the content of the listing and how the returned code is consumed. Only minor gaps remain (e.g. whether results are ordered, filtered, or tiered in any specific way, and any auth assumptions).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no parameter semantics to add. The description does usefully explain that the emitted `code` value is the input to the `engine` parameter of other fanbei tools, linking the outputs of this tool to the inputs of siblings.

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?

The description pairs a specific verb (列出/list) with a specific resource (可用于翻译的引擎) and further scopes it (模型档与传统网页引擎), so the agent knows exactly what comes back. It also distinguishes this enumeration tool from the action siblings by noting that the returned `code` feeds the `engine` parameter of other tools.

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: the closing sentence about `code` feeding other tools' `engine` parameter signals that this should be called before translating, but it never states when to call it versus the sibling translate/list tools or any prerequisites. No explicit when-not or alternative routing is given.

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