Skip to main content
Glama

Liuwangcun Chinese Compliance Tools

人民币金额大写转换

rmb-uppercase

人民币金额大写转换:数字金额转财务规范大写(如 12000.50 → 人民币壹万贰仟元伍角整),支持 ¥ 符号剔除、负数、两位小数、零位补位。合同、发票、报销、支票必备。 传入参数对象,返回确定性计算结果与依据。适用场景:模型算数不稳、法规口径易错时,调用它拿准确答案。

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": {
      "input": "<input>"
    },
    "name": "rmb-uppercase"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes数字金额,如 12000.50
expectNo可选:你认为的大写,填了就做一致性校验

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the output is a deterministic calculation result plus supporting basis, and that it handles ¥ symbols, negative numbers, two decimal places and zero padding. However, it does not cover invalid-input behavior, how decimals beyond two places are treated, or what the returned 'basis' contains.

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?

The definition is front-loaded with purpose and a concrete example, followed by supported formats, scenarios and return behavior. A few phrases such as '合同、发票、报销、支票必备' and '传入参数对象' are filler, but overall the content is dense and well ordered.

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 two-parameter deterministic conversion tool with no output schema or annotations, the description provides enough context to call it correctly, including an example input/output and edge-format support. It omits the optional expect consistency check and error-behavior details, which are minor but real 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 100%, so the input and optional expect parameters are already documented. The description adds some meaning about accepted input formats (¥ symbol removal, negatives, two decimals, zero padding) but never mentions the optional expect consistency-check parameter, which is a meaningful capability left to the schema.

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 states a specific verb and resource: converting numeric RMB amounts into financial-standard uppercase characters. The worked example (12000.50 → 人民币壹万贰仟元伍角整) makes the output unambiguous, and the tool is clearly distinct from the sibling contract/template tools.

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?

It gives clear usage context: essential for contracts, invoices, reimbursements and checks, and explicitly recommends calling it when model arithmetic is unstable or regulatory wording is error-prone. There are no explicit when-not-to-use conditions or named alternatives, but the use case is well-scoped.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.