Skip to main content
Glama

apex-dev

Qr generate

qr_generate
Read-onlyIdempotent

Generate a scannable ISO 18004 QR code (SVG vector and/or base64 PNG data URI) for any URL, wallet address, payment URI, or text up to 271 bytes. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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": {
      "text": "<text>"
    },
    "name": "qr_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
eccNoOptional error correction level: L, M (default), Q, or H.
sizeNoOptional image size in pixels (64-1024, default 256).
textYesText, URL, wallet address, or payment URI to encode.
formatNoOptional output format: svg (default), png, or both.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly/openWorld/idempotent/destructive=false) by disclosing the paid nature of the call: '$0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1)'. It also states a hard input ceiling of 271 bytes and the available output encodings, which the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences with zero filler: capability and output formats first, then price and payment rails, then the required call sequence. Each sentence carries information an agent needs before invoking the tool.

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

Completeness5/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 still names the return artifacts (SVG vector and/or base64 PNG data URI), and it covers cost, accepted payment methods, input size limit, and the payment handshake. Nothing essential for a correct first invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by stating the 271-byte ceiling on `text` and enumerating SVG and/or base64 PNG output, which contextualizes the `format` and `payment` parameters. It does not elaborate on `ecc` or `size` semantics beyond the schema, so it stops short of a 5.

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?

Specific verb plus resource: 'Generate a scannable ISO 18004 QR code (SVG vector and/or base64 PNG data URI)' with an explicit input domain of URL, wallet address, payment URI, or text. The standard cited (ISO 18004) and the concrete output encodings leave no ambiguity about what the tool produces, and no sibling in the list does QR generation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The two-step payment protocol is spelled out explicitly: 'Call once without `payment` for terms, then call again with `payment`.' This is the exact sequencing an agent would otherwise get wrong, and it states both the when and the when-again condition rather than leaving it to inference.

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