Skip to main content
Glama

Make My QR Codes

Make a free static QR code

make_static_code
Read-onlyIdempotent

Make a QR code without an account. The code holds the content itself (a web address, Wi-Fi login, text, email, phone or SMS), so it works offline and forever, but it can never be changed or counted after printing. Nothing is stored. Returns the image (SVG by default, or PNG).

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": {
      "type": "<type>"
    },
    "name": "make_static_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNotype "url": the web address the code opens, e.g. https://example.com/menu
ssidNotype "wifi": network name
textNotype "text": the message shown when scanned
typeYesWhat the code holds
labelNoOptional label under the code, e.g. "Scan for Wi-Fi"
styleNoDefault classic
formatNoDefault svg (best for print)
email_toNotype "email": address the new email goes to
email_bodyNo
sms_messageNotype "sms": text the message starts with
wifi_hiddenNotype "wifi": the network is hidden
phone_numberNotypes "phone" and "sms": the number to call or text
email_subjectNo
wifi_passwordNotype "wifi": password (leave out when wifi_security is "nopass")
wifi_securityNotype "wifi": WPA covers WPA2 and WPA3. Default WPA.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent safety; the description adds genuinely new behavior: content is encoded in the image, works offline, is immutable after printing, is not tracked, and nothing is persisted server-side. These are decision-critical facts an agent cannot derive from the annotations and prevent misuse for changing destinations.

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 account-free static premise, then the permanence trade-off, then the return format. No filler and no repetition of the schema.

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 15-parameter, no-output-schema tool, the description covers the essential decision facts and the return format. Minor gap: it says "Returns the image" without indicating whether that is binary data, a URL, or a file reference, which matters for a tool with no output schema.

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 87%, so the schema already documents nearly every field including the type-conditional ones. The description echoes the content categories and the SVG/PNG default but adds no syntax or conditional-requirement detail 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?

"Make a QR code without an account" gives a specific verb and resource, and the constraint that the content is embedded permanently distinguishes this from an account-based code generator. It stops short of naming create_code as the editable alternative, so the sibling differentiation is inferable rather than explicit.

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?

The conditions are clear: use this when no account is available and the destination is final and untracked. The trade-off sentence ("can never be changed or counted") effectively signals when not to use it, but the agent gets no explicit pointer to which sibling handles editable or trackable codes.

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