qrcode-pub-mcp

QR code image (free)

qr_code

Read-onlyIdempotent

Generate QR code images in PNG or SVG from any text or link, free and without an account. Get the image plus a permanent URL to embed or print.

Instructions

Generate a QR code image (PNG or SVG) for any text or link. Free, no account. The answer carries the image and a permanent image URL you can embed or print.

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	Description
`ecc`	No	Error correction (default M)
`data`	Yes	Text or URL to encode (max 2000 chars)
`size`	No	Pixels (default 300)
`color`	No	Foreground hex, e.g. 1a237e (default 000000)
`format`	No	Image format (default png)
`margin`	No	Quiet zone in modules (default 4)
`bgcolor`	No	Background hex, e.g. ffffff

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond that: no account is needed and the response carries both the image and a permanent, embeddable image URL, which is valuable output-shape information given no output schema exists.

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?

Two tightly written sentences with the core action front-loaded and the value-add (permanent URL, no account) following. Every clause carries information; nothing is redundant.

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 a 7-param tool with a fully documented schema, the description covers purpose, cost/auth model, and return shape. It omits no critical detail, though it could note size or ECC tradeoffs. Sufficient given the schema does the parameter heavy lifting.

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 the schema already documents all 7 parameters with defaults, ranges, and enums. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 image') plus the supported formats (PNG or SVG) and the input domain (any text or link). This clearly separates it from siblings like host_file, page_metadata, and page_to_markdown without opening any schema.

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 implied by the phrase 'for any text or link,' but the description never states when to prefer this tool over siblings or what conditions make it inappropriate. No exclusions or prerequisites beyond 'Free, no account.' Adequate but leaves routing to inference.

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

Deploy Server