Skip to main content
Glama

Ezkielyna Public Tools

QRIS ke gambar SVG / QRIS to SVG

qris_to_svg
Read-onlyIdempotent

Membuat gambar QR code (SVG) dari teks QRIS yang valid. Renders a valid QRIS payload as an SVG QR code (byte mode, error correction L/M/Q/H, default M). Built-in encoder, no dependencies, offline. Refuses invalid QRIS. Always test-scan the result before printing.

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": "qris_to_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
eccNoError correction level (default M).M
qrisYesThe QRIS payload text (starts with "000201" and ends with "6304" + 4 hex characters). Paste text, not an image.
marginNoQuiet zone in modules (4 recommended).
module_pxNoPixels per module (width/height attributes only; the SVG scales).
dark_colorNoModule colour #rrggbb (default #000000). Keep strong contrast.
light_colorNoBackground colour #rrggbb (default #ffffff).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower, and the description still adds real context: a built-in dependency-free offline encoder and explicit refusal of invalid QRIS. The test-scan warning is a useful operational caveat not captured anywhere in structured data.

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 and kept to a few short sentences. The Indonesian and English sentences largely duplicate each other, which costs some density, but the remaining content (encoder details, refusal, print warning) earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter generator with no output schema, the description never says what the call returns (raw SVG markup string? file?) or its size characteristics, beyond implying an SVG is produced. The refusal behavior is disclosed, but the response shape an agent must handle is left unspecified.

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 ecc, margin, module_px, and colors. The description adds only the encoding detail (byte mode) and restates the ECC default M, which the schema already declares; it does not explain tradeoffs such as higher ECC shrinking usable capacity.

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 ("Membuat gambar QR code (SVG) dari teks QRIS") plus the output format, so an agent can distinguish it from validate_qris/parse_qris by what it produces. It never names those siblings explicitly, so the differentiation is inferable rather than stated.

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 payload must be valid and invalid input is refused, and the user should test-scan before printing. There is no explicit routing guidance such as "run validate_qris first" or "use parse_qris to inspect fields," which would be valuable given the sibling set.

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