Skip to main content
Glama

Ezkielyna Public Tools

Hitung PPN / Indonesian VAT

hitung_ppn
Read-onlyIdempotent

Menghitung PPN Indonesia (aturan 2025+). Computes Indonesian VAT (PPN) from the price before tax, from DPP nilai lain, or backwards from a total that includes PPN. Default kategori nonmewah = 12% x DPP nilai lain 11/12 (effective 11%, PMK 131/2024 Pasal 3); mewah = 12% x price (Pasal 2); custom = your own rate/factor. Returns harga jual, DPP, PPN, total, the rule used and its source. Calculation aid, not tax advice.

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": {
      "nilai": "<nilai>"
    },
    "name": "hitung_ppn"
  }
}

Input Schema

NameRequiredDescriptionDefault
dariNoWhat "nilai" is: harga_jual (price/penggantian before PPN, default), dpp_nilai_lain (already the DPP), total (price including PPN).harga_jual
nilaiYesA JSON number, or text such as "1250000", "Rp1.250.000,50" or "1,5 jt". Send very large numbers (>= 2^53) as text.
kategoriNononmewah (default, 12% x 11/12), mewah (luxury goods, 12% x price) or custom (needs tarif_persen).nonmewah
faktor_dppNoOnly for kategori=custom: DPP factor, e.g. "11/12", 0.9 or "90%" (default 1).
pembulatanNoRound PPN to whole Rupiah: tidak (no, show sen), bawah (down), terdekat (nearest), atas (up).tidak
tarif_persenNoOnly for kategori=custom: rate in percent, e.g. 11 or "1,1".

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 declare readOnly/idempotent/non-destructive, so the description's job is to add rule context — and it does: it names the legal basis (PMK 131/2024 Pasal 3 and Pasal 2), explains the effective 11% outcome of 12% x 11/12, and lists what comes back (harga jual, DPP, PPN, total, rule used, source). The "not tax advice" caveat is a useful honesty signal; only minor gaps like rounding interaction with the legal rule are unstated.

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?

Dense but front-loaded: the purpose and the three modes lead, then defaults and formulas, then the return payload and disclaimer. No filler sentences, though the kategori rate rules partially duplicate what the schema already documents.

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?

With no output schema, the description compensates by enumerating the returned fields and the rule/source attribution. Combined with 100% schema coverage and stated defaults, an agent has enough to call this correctly and interpret the result.

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, but the description earns extra credit by explaining the formula behind each kategori value rather than just restating the enum labels (nonmewah = 12% x 11/12 DPP, mewah = 12% x price, custom = own rate/factor). This gives an agent the meaning of the choice, not merely its name.

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 ("Menghitung PPN Indonesia") and then enumerates the three computation directions (forward from pre-tax price, from DPP nilai lain, or backwards from a PPN-inclusive total). No sibling tool (parse_rupiah, format_rupiah, terbilang) could be confused with this one after reading it.

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?

Clearly signals when each input mode applies by tying `dari` values to their meanings (harga_jual, dpp_nilai_lain, total) and which kategori to pick, including that custom needs a user-supplied rate. It stops short of explicit exclusions or routing to siblings, but the mode-selection guidance an agent needs is present.

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