Skip to main content
Glama

Make My QR Codes

Download a code

download_code
Read-onlyIdempotent

A print-ready file of one of the account's codes: SVG (default, any size), PNG (up to 2000 px) or vector PDF at a set width in inches.

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": {
      "code": "<code>"
    },
    "name": "download_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code: its id from list_codes, or a changeable code's link ending (e.g. "menu" for makemyqrcodes.com/menu)
formatNo
size_pxNoPNG width, default 1200
width_inNoPDF width in inches, default 2

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description contributes beyond that by disclosing format-specific behavior: SVG is the default and scales to any size, PNG is capped at 2000 px, and PDF is vector at an inch-based width — useful constraints an agent would otherwise have to guess.

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 dense sentence with no filler; the output formats and their constraints are stated up front. Nothing in it could be cut without losing information.

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?

With four parameters, 75% schema coverage and no output schema, the definition covers inputs well but says nothing about what comes back — a file body, a URL, or base64 — which is the key unknown for a download tool. Error cases (e.g. PNG over 2000 px, non-existent code) are also unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description adds the one thing the schema omits: format defaults to SVG when unspecified. It also reinforces the semantic of each format's sizing unit (px for PNG, inches for PDF), which clarifies which size parameter applies to which format.

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?

The description names a specific deliverable — a print-ready file of one of the account's codes — and enumerates the three output formats. It does not use a verb like 'download' (that lives only in the title), and it never contrasts itself with get_code, so an agent must infer that this renders a file while get_code returns metadata.

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 'print-ready file': the agent can reason that this is the export path rather than the metadata path. However, no explicit when-to-use, when-not-to-use, or alternative (get_code) is named, and no prerequisites such as account plan or code type restrictions are stated.

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