Skip to main content
Glama

Ezkielyna Public Tools

Baca QRIS / Parse QRIS

parse_qris
Read-onlyIdempotent

Membongkar teks QRIS menjadi field bernama. Decodes a QRIS / EMVCo merchant-presented QR payload into named fields: static or dynamic, merchant accounts (tags 26-51, incl. NMID in the national QRIS template), MCC, currency, amount, tip/fee, country, merchant name/city, postal code, additional data (tag 62), language template and the CRC check. Offline, nothing is sent anywhere.

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>"
    },
    "name": "parse_qris"
  }
}

Input Schema

NameRequiredDescriptionDefault
qrisYesThe QRIS payload text (starts with "000201" and ends with "6304" + 4 hex characters). Paste text, not an image.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 still adds real context beyond them: it explicitly says the work is offline and 'nothing is sent anywhere', which confirms the closed-world, privacy-preserving behaviour, and it lists the output fields. It does not say what happens on an invalid or truncated payload.

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?

Front-loaded with the core action in both Indonesian and English, then a single dense enumeration of parsed fields. The bilingual opening is slightly redundant and the field list is long, but every clause carries information the caller needs.

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 pure-parsing tool with no output schema, the definition is nearly complete: it names the input format, the input kind (text, not an image), the full field set returned, and the offline guarantee. The only real gap is error behaviour on malformed payloads or CRC failures.

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% and there is a single required parameter whose format (starts with 000201, ends with 6304 plus four hex characters) is fully documented in the schema itself. The description only reinforces that it takes QRIS text; it adds no semantics beyond what the schema already supplies, so the baseline of 3 applies.

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?

Names a specific verb (decode/parse) and resource (QRIS/EMVCo merchant-presented payload) and enumerates the resulting fields, from static/dynamic type through CRC check, so an agent knows exactly what comes back. It never states how it differs from the similarly named validate_qris sibling, which is the only thing separating it from a 5.

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: the tool is clearly for turning a QRIS text payload into fields, and the schema note 'Paste text, not an image' nudges the caller toward the right input. There is no explicit statement about when to prefer validate_qris over parse_qris, or what to do when the CRC does not match.

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