Crypto, web, finance and app data tools

QR Code Generator

qr_code

Generate a QR code for any text, URL, wallet address or payment link as SVG or PNG, returned inline as SVG markup and a base64 data URI ready for HTML or chat. Choose size, border and error correction. Use when a user needs a scannable code for a link, Wi-Fi, contact or crypto 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": {
      "data": "<data>"
    },
    "name": "qr_code"
  }
}

Input Schema

Name	Required	Default
`data`	Yes
`size`	No
`border`	No
`format`	No	svg
`error_correction`	No	M

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does disclose the practically important behavior: results come back inline as SVG markup plus a base64 data URI usable in HTML or chat. It omits any statement about statelessness or limits on payload length, but the generation profile is clear.

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 sentences, all front-loaded: capability and accepted inputs first, output shape second, usage cue last. Every sentence contributes and 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?

An output schema exists, so return values needn't be explained, and the description still summarizes them helpfully. Combined with input domain and usage cue this is nearly complete; the remaining gap is clarification of the four optional parameters, especially the error-correction levels.

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 0%, so the description must compensate. It confirms format options (SVG/PNG) and names size, border, and error correction, but adds no meaning to size/border units or the L/M/Q/H levels for error_correction, which stay invisible to the agent.

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?

States a specific verb and resource ('Generate a QR code') plus the input domain (text, URL, wallet address, payment link) and output formats (SVG/PNG). No sibling in the list produces QR codes, and the description makes that scope unmistakable.

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?

Explicit when-to-use clause: 'Use when a user needs a scannable code for a link, Wi-Fi, contact or crypto payment.' There is no competing alternative tool to route against, so the absence of exclusions is acceptable, but the guidance stops short of when-not scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crypto, web, finance and app data tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?