Skip to main content
Glama

Ezkielyna Public Tools

Baca nominal Rupiah dari teks / Parse Rupiah

parse_rupiah
Read-onlyIdempotent

Membaca nominal dari teks berantakan. Extracts a number from messy text: "Rp 1.250.000,-", "IDR 50k", "1,5 jt", "2.5M", "(Rp1.000)", "Total: Rp1.234.567,89" or words like "dua juta lima ratus ribu rupiah". Indonesian conventions first ("." thousands, "," decimal); ambiguities are reported.

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": {
      "teks": "<teks>"
    },
    "name": "parse_rupiah"
  }
}

Input Schema

NameRequiredDescriptionDefault
teksYesText that contains an amount.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 is covered. The description adds real behavioral context beyond that: Indonesian conventions are applied first ('.' thousands, ',' decimal) and ambiguities are reported rather than silently guessed. It stops short of describing the return shape, which matters since no output schema exists.

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?

Two sentences with the purpose front-loaded and the examples doing efficient work in a compact list. The bilingual opening duplicates the same information in Indonesian and English, which adds slight redundancy but also aids matching against Indonesian-language queries.

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 one-parameter parser with no output schema, the description covers input variety, convention priority, and ambiguity handling. The main remaining gap is what the parse result looks like (number only, or number plus confidence/ambiguity flag), which the phrase 'ambiguities are reported' only hints at.

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?

With a single required parameter at 100% schema coverage, the schema already documents 'text that contains an amount'. The description adds value by enumerating the accepted input forms - prefixed amounts, shorthand like '50k' and '1,5 jt', magnitudes like '2.5M', parenthesized negatives, and spelled-out numbers such as 'dua juta lima ratus ribu rupiah' - which materially widens the agent's understanding of valid input.

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?

States a specific verb and resource ('extracts a number from messy text') and pins the direction of conversion with concrete inputs such as 'Rp 1.250.000,-' and '1,5 jt'. That direction (text -> number) makes it clearly distinct from the inverse sibling format_rupiah without needing to name it.

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 strongly implied by the sample inputs, so an agent can infer this is the tool for pulling an amount out of unstructured text. However, it never states when to prefer it over siblings (e.g., format_rupiah for the reverse direction) nor any exclusion or input precondition, so guidance stays implicit.

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