QRStuff MCP Server

Scan QR code

scan_qr_code

Read-onlyIdempotent

Use this when the user shares a picture of a QR code and wants to know what it contains or where it leads. Reads every QR code in a PNG, JPEG or WebP image and returns the decoded content and its type (link, Wi-Fi, contact, event, email, phone, payment, text). Read-only; creates nothing. Do not use it for counting how many times a code was scanned (use get_qrcode_scans) or for business cards (use scan_business_card).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scan_qr_code"
  }
}

Input Schema

Name	Required	Description	Default
`image`	No	The attached image containing the QR code.
`base64_image`	No	The image containing the QR code as base64 (PNG, JPEG or WebP), for clients that cannot attach files. Send either image or base64_image.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces with 'Read-only; creates nothing'. It adds genuine context beyond annotations: it reads EVERY QR code in the image and returns both decoded content and a typed classification (link, Wi-Fi, contact, etc.), which helps the agent interpret results.

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 tightly constructed sentences, front-loaded with the trigger, then behavior, then exclusions. No filler and every sentence carries routing or behavioral information.

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?

With an output schema present, return values need not be restated, and the description covers the input trigger, format handling, return shape at a high level, and sibling exclusions. Nothing an agent needs to call it correctly is missing.

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 100%, so both `image` and `base64_image` are already documented in the schema, including the PNG/JPEG/WebP formats and the image-or-base64 choice. The description's mention of formats is redundant with the schema, so 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?

Specific verb (reads/decodes) plus resource (QR codes in an image), with the return content and its type enumeration spelled out. It is clearly distinguishable from sibling generation tools (generate_qr_code, create_static_qr_code) because it consumes an image rather than producing one.

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?

Names the trigger condition ('user shares a picture of a QR code and wants to know what it contains') and two explicit exclusions with the correct alternatives: `get_qrcode_scans` for scan counts and `scan_business_card` for business cards. An agent can route without inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All QRStuff MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?