Skip to main content
Glama

Generate QR code

generate_qr_code
Read-only

Generates a QR code image (PNG) for a URL or any short text, for example a website address or Wi-Fi details.

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": {
      "text": "<text>"
    },
    "name": "generate_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoImage width and height in pixels (128-1024).
textYesThe URL or text to encode in the QR code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), so the bar is lower. The description adds genuinely new information not in the annotations or schema: the output artifact is a PNG image, which matters because no output schema exists. It omits details like whether the image is returned inline or via URL/path.

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?

A single front-loaded sentence with the verb and output format first, followed by the input domain and examples. No redundant or filler phrasing; every clause adds usable information.

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 simple two-parameter generation tool with full schema coverage and clear annotations, the description covers purpose, input domain, and output format. The only meaningful gap is how the resulting PNG is delivered (inline data, URL, or file), which an agent might want before calling.

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 both parameters are already documented in the schema, making 3 the baseline. The description reinforces the meaning of `text` with input examples (URL, Wi-Fi details) but says nothing about `size` beyond what the schema specifies.

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?

States a specific verb and resource ("Generates a QR code image (PNG)") plus the input domain (URL or short text), so an agent immediately knows what it produces. It does not name or differentiate from siblings, though the sibling list (generate_password, calculate_emi, count_words, format_json) makes overlap unlikely.

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 through the examples "a website address or Wi-Fi details," which give a sense of appropriate inputs. There is no explicit when-to-use/when-not guidance or stated alternatives, so selection must be inferred from the purpose line.

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