Skip to main content
Glama

QR Code Generator - link, text, Wi-Fi, SEPA payment (PNG + SVG)

qr_code_generator
Read-onlyIdempotent

Make a QR code that never expires and has no tracking: link or text, Wi-Fi login (WPA/WEP), or an EPC SEPA payment QR (GiroCode) that banking apps scan to pre-fill a transfer. Returns PNG (base64) and SVG, custom color. Runs on our server, < 0.2 s. Free: 25 calls/day per IP. Paid: $0.001 per call via x402 at https://radarbg.com/x402/qr-code-generator.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "kind": "link",
      "text": "https://radarbg.com"
    },
    "name": "qr_code_generator"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoReceiver BIC (optional)
ibanNoReceiver IBAN (kind=sepa)
kindNolink, wifi or sepalink
ssidNoWi-Fi name (kind=wifi)
textNoLink or text (kind=link), max 1,500 characters
colorNoHex color, e.g. #000000
payeeNoReceiver name (kind=sepa)
amountNoEUR amount, e.g. 25.50 (kind=sepa)
passwordNoWi-Fi password (kind=wifi)
securityNoWPA, WEP or nopassWPA
referenceNoPayment reference (kind=sepa)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: no expiry, no tracking, server-side execution under 0.2 s, and concrete rate/cost limits (25 calls/day free, $0.001 per call via x402). That is solid added value, though the return payload is only named, not characterized.

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 capability and mode list, then behavior, then limits and pricing. It is a single dense paragraph with no wasted sentences, though the pricing URL and latency figure make it slightly crowded.

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 an 11-parameter tool with no output schema, the description covers return formats (PNG base64 and SVG), execution model, and cost limits, which is most of what an agent needs. It leaves conditional parameter dependencies implicit, a minor gap given the fully documented schema.

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%, so every parameter is already documented, and the baseline is 3. The description adds modest meaning by explaining that the sepa kind produces a GiroCode that pre-fills a transfer and that output is PNG base64 plus SVG with custom color, but it does not clarify conditional requirements (e.g. iban/payee needed for sepa, ssid/password for wifi).

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 concrete verb and resource ('Make a QR code') and enumerates the three supported modes (link/text, Wi-Fi WPA/WEP, EPC SEPA GiroCode), so an agent knows exactly what it produces. It does not differentiate itself from the sibling barcode_generator, which is the only thing keeping 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for each mode — Wi-Fi login credentials, or a SEPA payment that banking apps pre-fill — which effectively tells the agent which kind to pick. It stops short of explicit when-not guidance or naming an alternative tool for non-QR barcode needs.

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