Skip to main content
Glama

Ezkielyna Public Tools

Terbilang (angka ke kata)

terbilang
Read-onlyIdempotent

Mengubah angka menjadi kata-kata Bahasa Indonesia (terbilang) untuk kuitansi/invoice. Converts a number to Indonesian words: up to 999 kuadriliun, decimals with "koma", negatives, optional "rupiah" suffix and "sen", correct seratus/seribu/sebelas rules. Example: 1500 -> "seribu lima ratus".

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": {
      "angka": "<angka>"
    },
    "name": "terbilang"
  }
}

Input Schema

NameRequiredDescriptionDefault
senNoWith rupiah=true: read up to 2 decimals as sen ("... rupiah lima puluh sen") instead of "koma".
angkaYesA JSON number, or text such as "1250000", "Rp1.250.000,50" or "1,5 jt". Send very large numbers (>= 2^53) as text.
hurufNoLetter case: kecil (lower), awal (first letter), judul (Title Case), besar (UPPER).kecil
rupiahNoAppend "rupiah".
kata_negatifNoWord used for negative numbers.minus

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnly/idempotent/non-destructive and closed-world, so safety is covered. The description adds real behavioral value beyond them: the numeric ceiling (999 kuadriliun), how decimals are verbalized ("koma"), negative handling, and the seratus/seribu/sebelas spelling rules. It stops short of describing any error behavior for out-of-range or unparseable input.

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 sentences, front-loaded with the core transformation and scope, ending on a compact example that anchors the output format. The bilingual restatement is the only mild redundancy and it earns its place for an Indonesian-language utility.

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?

For a single-value, read-only converter with full schema documentation and no output schema, the description supplies everything needed: what goes in, the range limit, how decimals/negatives are handled, and a sample of the returned string. Nothing essential to correct invocation is missing.

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 would be 3; the description still earns credit by showing a concrete input→output mapping (1500 -> "seribu lima ratus") and explaining the Indonesian numeral rules that govern how angka is rendered. It does not restate the sen/rupiah interaction rules beyond what the schema already spells out.

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 specific verb and resource ("Mengubah angka menjadi kata-kata Bahasa Indonesia") and pins the scope with bounds (up to 999 kuadriliun, decimals, negatives) plus a worked example. It does not name or distinguish itself from the nearby currency siblings (format_rupiah, parse_rupiah), so an agent must infer that this one returns words rather than a formatted numeric string.

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?

"untuk kuitansi/invoice" gives a clear usage context, and the optional-feature list (rupiah suffix, sen, kata_negatif) implies when to enable each. There are no explicit exclusions or named alternatives telling the agent when to prefer parse_rupiah/format_rupiah instead.

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.

Resources