Skip to main content
Glama

Ezkielyna Public Tools

QRIS statis jadi dinamis / Set QRIS amount

set_qris_amount
Read-onlyIdempotent

Mengubah QRIS STATIS menjadi DINAMIS dengan nominal Rupiah. Turns a valid STATIC QRIS into a DYNAMIC one with a fixed amount in whole Rupiah: sets tag 01 to 12, inserts tag 54, optionally adds a tip/fee (tags 55-57, off by default) and recomputes the CRC. Refuses invalid or already-dynamic input. This only rewrites text: it does not move money, and the result is only as valid as the merchant's static code.

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

Input Schema

NameRequiredDescriptionDefault
tipNoTip/convenience fee: none (default), prompt (payer types a tip, 55=01), fixed (55=02 + 56), percent (55=03 + 57).none
qrisYesThe merchant's own STATIC QRIS payload text.
amountYesAmount in whole Rupiah, e.g. 15000 or "15.000". Max 13 digits.
tip_valueNoFor tip=fixed: whole Rupiah. For tip=percent: 0.01-99.99.
allow_dynamic_inputNoAllow a QRIS that is already dynamic (its amount is replaced). Off by default because dynamic codes are usually single-use.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description discloses refusal behavior for invalid/already-dynamic input, that tip tags are off by default, that the CRC is recomputed, and that no funds move. It also warns that output validity is bounded by the merchant's source code, which annotations cannot convey.

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 transformation and its scope are front-loaded in the first clause, and the caveat sentence earns its place by preventing misuse. There is mild redundancy from the Indonesian and English restating the same operation, which slightly dilutes density.

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 5-parameter text-transform tool with no output schema, the description covers inputs, refusals, tip defaults, and side-effect boundaries well. It stops short of saying what the return value looks like (presumably the rewritten payload string), which an agent calling it would want to know.

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 coverage is 100%, so the schema already documents every parameter including tip modes and tag mappings. The description reinforces the tip/fee tags and the off-by-default posture but adds no syntax or format detail beyond what the schema states, so baseline 3 applies.

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 names a specific transformation (STATIC QRIS -> DYNAMIC) with a fixed Rupiah amount, and enumerates the exact payload edits (tag 01 = 12, insert tag 54, optional 55-57, CRC recompute). It also draws a clear boundary ('only rewrites text, does not move money') that separates it from money-moving or validation 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 states clear preconditions and exclusions: input must be a valid STATIC code, invalid or already-dynamic input is refused, and dynamic input requires allow_dynamic_input with a rationale (dynamic codes are usually single-use). It does not explicitly route agents to parse_qris or validate_qris for inspection, so it falls short of full alternative naming.

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