Skip to main content
Glama

Image Resize & Convert Tools (Tanod)

make_qr_code

Idempotent

utilpeek: make a QR code image. For 1-D barcodes use make_barcode; to read a code use read_qr_barcode. Returns svg (text) or data_base64 (PNG), or with output "url" a 24 h download link, plus version, modules, width_px, height_px and bytes. Data too long for a QR code at the chosen level is a 422 (not charged). Encoded locally, nothing is fetched; typically under 0.1 s. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/qr-code-api.html

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": {
      "data": "<data>"
    },
    "name": "make_qr_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesText or URL to encode (1-2000 characters, at most 2953 UTF-8 bytes).
errorNoError correction level.M
scaleNoPixels per module.
borderNoQuiet zone in modules.
formatNosvg (text) or png (base64).svg
outputNobase64 (default): inline. url: stored for 24 hours; link, metadata.base64

Output Schema

NameRequiredDescriptionDefault
svgNo
bytesNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
scaleNo
borderNo
formatNo
modulesNo
versionNo
verifiedNo
width_pxNo
height_pxNo
data_base64No
verified_byNo
verify_noteNo
content_typeNo
decoded_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / border / description
      Previous value: -"Quiet zone in modules (0-10, default 4)."New value: +"Quiet zone in modules."
    • removedInput schema / properties / border / title
      Removed value: -"Border"
    • removedInput schema / properties / data / title
      Removed value: -"Data"
    • changedInput schema / properties / error / description
      Previous value: -"Error correction level (default M)."New value: +"Error correction level."
    • removedInput schema / properties / error / title
      Removed value: -"Error"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / output / title
      Removed value: -"Output"
    • changedInput schema / properties / scale / description
      Previous value: -"Pixels per module (1-20, default 8)."New value: +"Pixels per module."
    • removedInput schema / properties / scale / title
      Removed value: -"Scale"
    • removedInput schema / title
      Removed value: -"make_qr_codeArguments"
  2. Changed1 schema field changed
    • changedInput schema / properties / output / description
      Previous value: -"base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window."New value: +"base64 (default): inline. url: stored for 24 hours; link, metadata."
  3. Changed4 schema fields changed
    • addedOutput schema / properties / decoded_text
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / verified
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / verified_by
      Added value: +{
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / verify_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / output
      Added value: +{
      +  "default": "base64",
      +  "description": "base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window.",
      +  "enum": [
      +    "base64",
      +    "url"
      +  ],
      +  "title": "Output",
      +  "type": "string"
      +}
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "border": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "bytes": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "content_type": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "data_base64": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "format": {
      +      "enum": [
      +        "svg",
      +        "png",
      +        null
      +      ],
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "height_px": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "modules": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "scale": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "svg": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "version": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "width_px": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  6. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations it discloses cost (USD 0.001), the free quota (10 calls/IP/UTC day), the 422-not-charged behavior, local encoding with "nothing is fetched", and sub-0.1 s latency, plus the 24 h persistence of url output. The only gap is that "encoded locally, nothing is fetched" sits slightly at odds with openWorldHint=true and with url output being stored, without reconciling how/where the link is hosted.

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?

Dense but front-loaded: purpose first, then sibling routing, then return shape, then limits/pricing/docs. Every sentence carries actionable information and nothing is repeated from the schema verbatim.

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

Completeness5/5

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

An output schema exists, yet the description still summarizes the return keys, error semantics, latency, persistence, and cost. Combined with full schema coverage and annotations, nothing an agent needs to call this correctly and interpret the result is missing.

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 100%, so the baseline is 3, but the description adds value by tying parameter choices to returned fields (format svg yields `svg` text, png yields `data_base64`, output "url" yields a 24 h link). It does not elaborate on `error`, `scale`, or `border`, but the schema already covers those fully.

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?

The opening sentence names a specific verb and resource ("make a QR code image") and immediately disambiguates from two sibling tools by naming them and their domains (1-D barcodes, reading). An agent knows exactly what this tool produces without opening the schema.

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?

It gives explicit routing rules: use make_barcode for 1-D barcodes and read_qr_barcode to read a code. It also states the failure boundary (data too long for the chosen level yields a 422) which lets an agent anticipate and recover rather than retry blindly.

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.