Skip to main content
Glama

账户余额

fanbei_account
Read-only

Check the current token's account credit balance, account validity period, and token expiration time before placing translation orders or verifying access.

Instructions

查询当前令牌对应账号的积分余额、有效期与令牌到期时间。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 the safety profile is covered. The description adds that scope is fixed to the current token's account and that it is a passive state read, but it does not say what happens on an expired or invalid token, nor whether a zero/no-expiry value is possible.

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?

A single sentence with the resource list front-loaded and no filler, boilerplate, or restatement of the title. Every clause (balance, validity, token expiry) earns its place by naming a distinct returned field.

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 output schema, the description properly enumerates the three return values an agent would want. It omits units/format for the credit balance and any note on error or expiry states, which is a minor but real gap for a zero-argument diagnostic tool.

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 there is no parameter meaning the description needs to supply and the baseline of 4 applies. The description correctly indicates that account identity is derived from the token rather than passed in.

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 names a specific verb (查询) plus three concrete resources: 积分余额, 有效期, and 令牌到期时间. It is unmistakably distinct from every listed sibling (download, engines, list_tasks, quote, task_status, translate_document), none of which return account state.

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?

The phrase 当前令牌对应账号 makes the operating context clear: this reads state for the caller's own token, with no account selector, so there is nothing to choose. It stops short of explicit when-to-call guidance, such as checking balance before a paid operation like fanbei_translate_document or fanbei_quote.

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