Skip to main content
Glama

QR Code Reader API - decode QR codes from an image

qr_code_reader
Read-onlyIdempotent

Find and decode every QR code in a photo or screenshot: content, type (link, Wi-Fi, SEPA, text...), position. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/qr-code-reader.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileName": "qr.png",
      "fileContent": "iVBORw0KGgoAAAANSUhEUgAAAhAAAAIQAQAAAAD4e2okAAABlUlEQVR42u3dQU4DMQwF0BH3vzMsEEq+nXRTCYH8RqKo0/AWWXw5TqY8n29fDwKBQCAQCAQCgUAgEAjErxBPXOvuer2N+XjevhAIxH8gSjJkSnx//vN6GiMvEIipebESIlNjfV7HyAsEQl6sqmIfJS8QCHnxur7Y+xfyAoGQF703kRlx63HICwRiZl7k3fPP6S9NJwIxLS/aRmvUEq9Gmk4EYl5erHd75yLrjbqrKi8QiKnrkXtVse+truSQFwjE3PVIntPqFcb6rd+JQKgvsnKo3dDe2ZAXCMTMvDjtf/Qehv1UBEJeZArsK5M87Vl7o/ICgZi7HtmrjDwV3rue8gKBmFxf9GfYT1mif4FAqC9uZzqzs1HTxHQiEHPri/v58N7hkBcIxNz6otYQmRfnZ89MJwIxLy9Oe6X7aqSf9JQXCMTcvMi1x3p3qj3kBQIhL3LN0c9e1KdH5AUCIS8yI7LWUF8gEPKiZkc/gZF35QUCMTUv+t3zd/TVEximE4GYlhf+dxMCgUAgEAgEAoFAIBCIP0p8AYpI1hVg0lZtAAAAAElFTkSuQmCC"
    },
    "name": "qr_code_reader"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOr several files: [{fileName, fileContent (base64)}]
fileNameNoFile name with extension, e.g. report.pdf
fileContentNoThe file as base64 (a data: URI is fine)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: server-side execution, immediate file deletion with nothing stored, a 25 calls/day free tier, and per-call pricing via x402. It does not describe pagination or error behavior, keeping it just short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core capability is front-loaded in the first sentence, with privacy and pricing details following. It is dense but every clause carries information; the pricing URL is slightly operational clutter but not wasteful.

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?

With no output schema, the description compensates by naming the return fields (content, type, position). Combined with privacy and quota disclosure, an agent has enough to call it correctly; only error/edge-case behavior is unaddressed.

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 fileName, fileContent, and the files array are already documented in the schema. The description adds no format or syntax detail beyond that, so the baseline 3 applies.

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 ('Find and decode every QR code in a photo or screenshot') and enumerates the returned fields (content, type, position). This clearly distinguishes it from the sibling qr_code_generator, which produces rather than reads codes.

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?

The description makes the input context clear (photo or screenshot) and implies usage, but gives no explicit when-to-use/when-not-to-use guidance or named alternatives. The pricing and quota lines are operational, not selection guidance.

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