Pretty QR

Host a file

create_file_upload

Start hosting a photo, video, audio file or PDF for a hosted file QR code (up to 10 files per account). Returns a one-time upload_url (valid 30 minutes) and the file_url the file will have. Upload the raw file with the returned curl command, then call create_qr_code with content set to file_url. Counts as one QR API request.

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": "create_file_upload"
  }
}

Input Schema

Name	Required	Description	Default
`file_name`	No	Name of the file, e.g. menu.pdf. Shown when someone downloads it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

With no annotations present the description carries the full burden and does so well: it discloses the one-time upload_url with a 30-minute validity, the returned file_url, the 10-file-per-account limit, and that the call counts as one QR API request. These are exactly the traits an agent needs before committing a request.

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?

Two tight sentences, front-loaded with what the tool does and then the exact call sequence. Every clause carries non-redundant information: lifetime, limit, return values, and next step.

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?

For a one-parameter creation tool with no annotations or output schema, the description covers the full lifecycle from upload through the follow-up create_qr_code call, including expiry and quota. Nothing essential to calling 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?

There is only one parameter and schema description coverage is 100%, with the schema already explaining that file_name is shown on download. The description adds nothing about file_name, so this is the baseline case where the schema does all the work.

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+resource ('Start hosting a photo, video, audio file or PDF'), scopes it to hosted file QR codes, and immediately positions it as a precursor to create_qr_code, so it is unambiguous against siblings like list_templates or open_in_editor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit operational sequence: get upload_url and file_url, upload the raw file with the returned curl command, then call create_qr_code with content set to file_url. It also states the account cap of 10 files. It stops short of naming when-not-to-use or an alternative hosting path, so it falls just short of a 5.

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

All Pretty QR 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?