Skip to main content
Glama

Vietnam Payroll and Tax Calculator

Amount in words (Vietnamese and English)

amount_in_words
Read-onlyIdempotent

Write a whole number or VND amount (0 to 10^15) in words, in Vietnamese (as on invoices and payment orders: lẻ or linh for a zero tens digit, mốt, tư, lăm; nghìn, triệu, tỷ; optional "đồng chẵn") and in English. Examples: {"amount":1234567891}; {"amount":105,"language":"vi","vi_zero":"linh"}; {"amount":25000000,"vi_chan":true,"capitalize":true}.

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": {
      "amount": "<amount>"
    },
    "name": "amount_in_words"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesWhole number from 0 to 10^15, e.g. 1234567891.
vi_chanNoVietnamese only: end with "đồng chẵn" (an exact amount), as on payment documents. Default false.
vi_zeroNoVietnamese word for a zero tens digit: "lẻ" (default) or "linh", e.g. 105 = một trăm lẻ năm.
currencyNoAppend the currency ("đồng" / "dong"). Default true; false gives the bare number.
languageNo"vi", "en" or "both" (default).
capitalizeNoCapitalize the first letter. Default false.

Output Schema

NameRequiredDescriptionDefault
enNo
viNo
amountYes
disclaimerYes
data_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds domain-specific behavior beyond that: the valid range, Vietnamese formatting conventions such as lẻ/linh, mốt, tư, lăm, and optional đồng chẵn, plus examples of how options interact.

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 purpose and range are front-loaded, and the JSON examples are useful rather than decorative. The single sentence is dense and somewhat long, but it does not waste words or bury the main point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has only one required parameter, six documented parameters at 100% schema coverage, and an output schema, so the description need not explain return values. It supplies the remaining context an agent needs: range, language options, Vietnamese formatting quirks, and representative calls.

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?

Schema coverage is 100%, so the baseline is 3. The description still adds value by showing concrete parameter combinations, including vi_zero, vi_chan, capitalize, and language defaults, which helps an agent understand intended usage beyond the schema's already complete field descriptions.

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: write a whole number or VND amount in words in Vietnamese and English. It also gives the numeric range 0 to 10^15, which makes the scope unambiguous and clearly distinct from the payroll/tax calculators among its siblings.

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 identifies the practical context, namely invoices and payment orders, and the examples show typical invocations. It does not explicitly state when not to use it or name alternatives, but the tool is specialized enough that this is a minor gap.

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.