Skip to main content
Glama

Ezkielyna Public Tools

Validasi QRIS / Validate QRIS

validate_qris
Read-onlyIdempotent

Memeriksa struktur dan CRC QRIS. Validates a QRIS payload: TLV structure, mandatory fields, value formats and the CRC-16/CCITT (init 0xFFFF) checksum. Reports every problem found (errors and warnings) with a code and a fix hint. Offline.

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": "validate_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.5/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 safety and idempotency are covered. The description still adds real value by disclosing the output shape (every problem reported with a code and fix hint) and the exact checksum variant with init value. It stops short of saying whether a passing payload yields an empty problem list or an explicit OK status.

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 purpose, followed by the specific checks, then output behavior and the offline note. The Malay/English duplication costs a few words but serves bilingual clarity; nothing is padded.

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?

With no output schema, the description usefully covers what comes back: problem entries with codes and fix hints, spanning errors and warnings. Combined with the fully documented single parameter, an agent has what it needs to invoke the tool correctly; only the success-path return shape is unstated.

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?

There is a single parameter and schema description coverage is 100%; the schema already explains the expected text format, the '000201' prefix, and the '6304' + hex suffix. The description adds no syntax or format meaning beyond that, 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?

States a specific verb and resource: validates a QRIS payload, checking TLV structure, mandatory fields, value formats, and CRC-16/CCITT checksum. That is far more specific than the name alone. It does not, however, explicitly differentiate itself from the sibling parse_qris, which an agent might reasonably confuse with 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 only implied: an agent can infer this is the pre-flight check before parsing, and 'Offline' signals no network dependency. There is no explicit when-to-use statement and no named alternative such as parse_qris for agents who want extracted fields rather than diagnostics.

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