Skip to main content
Glama

Ezkielyna Public Tools

Format Rupiah

format_rupiah
Read-onlyIdempotent

Memformat angka sebagai Rupiah gaya Indonesia. Formats a number as Rupiah: "Rp1.234.567,89" (dot thousands, comma decimals), with or without "Rp", fixed decimals, ",-" suffix, or compact like "Rp1,2 jt" / "Rp1,2 juta".

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": "format_rupiah"
  }
}

Input Schema

NameRequiredDescriptionDefault
angkaYesA JSON number, or text such as "1250000", "Rp1.250.000,50" or "1,5 jt". Send very large numbers (>= 2^53) as text.
spasiNoSpace after Rp ("Rp 1.000"). Indonesian spelling rules (EYD) write it without a space.
simbolNoPrefix "Rp".
desimalNoDecimals 0-4, or "auto" (default: 0 for whole numbers, else 2). Rounds half up.
ringkasNoCompact: rb / jt / M / T (e.g. "Rp1,2 jt").
akhiran_stripNoAdd ",-" (e.g. "Rp1.000,-"); only with 0 decimals.
ringkas_desimalNoMax decimals in compact mode (trailing zeros dropped).
ringkas_panjangNoCompact with full words: ribu / juta / miliar / triliun.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile needs no restating. The description adds the concrete rendering behavior — dot thousands separators, comma decimals, and the compact variants — which is genuinely useful beyond annotations, but it says nothing about edge behavior such as how non-numeric or ambiguous text input like "1,5 jt" is handled, which the schema hints at but does not explain.

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 format and example are front-loaded in the first clause, and every listed variant corresponds to a real parameter. It loses a little to the bilingual duplication, where the Indonesian sentence largely restates the English one rather than adding information.

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 an 8-parameter pure formatting utility with no output schema, the description gives the agent enough to predict the returned string shape and to choose among the main output modes. The remaining parameters are fully documented in the schema, so nothing critical is missing, though the default decimal behavior is left entirely to the schema.

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 description coverage is 100%, so the baseline is 3. The description repeats the schema's own examples for the compact modes ("Rp1,2 jt" / "Rp1,2 juta") and the ",-" suffix, adding emphasis but no new meaning, and it never touches spasi or ringkas_desimal.

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 ("Formats a number as Rupiah") and immediately anchors it with a literal output example "Rp1.234.567,89". An agent can tell this apart from the sibling parse_rupiah (parsing input text) without opening either schema, since the direction of conversion is unambiguous.

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 through the enumeration of output variants (optionally prefixed with "Rp", fixed decimals, ",-" suffix, compact forms). There is no explicit statement of when to prefer this tool over parse_rupiah, nor any exclusion or prerequisite, so the agent must infer the routing from the verb alone.

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