JustQRs

Make a QR code image (free)

make_qr_code_image

Read-only

Render a static QR code as an image — no account or API key needed. Returns the image plus a shareable link to it. Static codes encode the content directly: they can't be edited after printing and scans aren't tracked (use create_qr_code with an API key for that). Kinds: url, text, phone, sms, email, wifi, vcard. No logos.

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": {
      "content": "<content>"
    },
    "name": "make_qr_code_image"
  }
}

Input Schema

Name	Required	Description	Default
`size`	No
`design`	No	Optional colors and styles; logo not allowed.
`format`	No		png
`content`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026
- addedInput schema / properties / content / type
```
Added value: +"object"
```
- addedInput schema / properties / design / type
```
Added value: +"object"
```
First observedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare a safe read-only, closed-world operation, yet the description adds real value: no auth required, the return includes a shareable link, codes are immutable after printing, scans are untracked, and logos are unsupported. It stops short of covering error behavior, rate limits, or output format details (png vs svg payload), which keeps it at 4.

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?

Four short sentences with the core action and the key constraint (free/static) front-loaded, followed by return value, limitations, and alternatives. Nothing is redundant with the annotations.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested design objects and no output schema, the description covers content kinds and return shape but omits the png/svg `format` parameter and gives no sense of the design surface beyond a logo prohibition. Adequate, but an agent could easily miss the svg export option.

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 only 25% across four params with deep nesting. The description compensates for the most important piece — enumerating the seven content kinds — but says nothing about the `format` (png/svg) or `size` parameters, and only alludes to `design` via 'No logos'.

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 ('Render a static QR code as an image') and immediately scopes it as free/no-account. It distinguishes itself from the dynamic sibling create_qr_code by naming the alternative outright, so an agent can choose between them without opening the schemas.

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?

Explicitly covers when to use this tool (static, print-once codes, no credentials) and when not to (editable or scan-tracked codes → create_qr_code with an API key). The exclusion plus named alternative satisfies the top bar.

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

All JustQRs tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?