Skip to main content
Glama

qr: QR codes that never expire

Create a QR code

create_qr_code

Create a dynamic QR code for a link. The code never expires and its target can be changed later. Returns the short URL, PNG/SVG image URLs and the QR image. Without an API key it also returns an edit_url: give that to the user, it is their only way to change the code later.

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": {
      "target_url": "<target_url>"
    },
    "name": "create_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoOptional look. Dark colors only; every style is test-scanned.
titleNoOptional name, e.g. "Poster Westbahnhof"
target_urlYesFull http(s):// URL the code should open

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=false, destructiveHint=false, idempotentHint=false and openWorldHint=false, so the write/safety profile is covered. The description usefully adds durability ("never expires"), mutability of the target, and the exact return contents including edit_url as the sole recovery path. It does not warn that non-idempotent calls create a new code each time, which is the main behavioral risk of this tool.

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, front-loaded with the purpose, then durability, then the return payload, then the critical edit_url caveat. No filler and every sentence carries distinct information an agent needs.

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?

With no output schema, the description does the work of describing returns (short URL, PNG/SVG URLs, image) and the conditional edit_url, which is exactly the missing piece. Minor gaps remain around repeated-call duplication and any auth/rate-limit behavior when an API key is present.

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 explains target_url, title and the nested style object (colors, emoji, shape, corners). The description adds only the loose framing "for a link" and nothing about style constraints beyond what the schema states, so baseline 3 applies.

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?

Specific verb+resource ("Create a dynamic QR code for a link") with the key differentiator "dynamic" spelled out as "its target can be changed later", and the return payload is enumerated. It stops short of explicitly distinguishing itself from siblings like create_qr_codes_bulk or update_qr_code, so a 4 rather than 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 Guidelines3/5

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

Gives a concrete operational instruction for the no-API-key case ("give that to the user, it is their only way to change the code later"), which is genuine usage guidance. However it never says when to pick this over the bulk-creation or update siblings, leaving alternative selection implicit.

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.