QRStuff MCP Server

Get batch sample file

get_batch_sample_file

Read-onlyIdempotent

Use this when the user wants to create many QR codes or short links from a spreadsheet and needs the template. Returns a download link to an XLSX template for the chosen types. Read-only.

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_types": "<data_types>"
    },
    "name": "get_batch_sample_file"
  }
}

Input Schema

Name	Required	Description	Default
`batch_type`	No	qrcode for QR codes or short_link for short links.	qrcode
`data_types`	Yes	QR code types the spreadsheet should cover, for example URL or PDF.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and the description's 'Read-only' merely restates that. It does add useful context that the result is a download link rather than the file contents. No detail on link expiry or formatting requirements beyond the enum.

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 short sentences with the trigger condition front-loaded and zero filler. Every sentence contributes: when to use, what it returns, and safety profile.

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?

For a two-parameter read tool with an output schema and full annotation coverage, the description is sufficient. The return format (download link to XLSX) is stated explicitly, though nothing explains what happens with the template afterward.

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% and the schema documents both batch_type (enum) and data_types. The phrase 'for the chosen types' loosely ties data_types to the spreadsheet contents but adds no format or item-level detail beyond the schema.

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?

States a specific verb and resource: returns a download link to an XLSX template for bulk QR code / short link creation. Clearly distinct from siblings like submit_batch or generate_qr_code. Lacks only an explicit contrast naming those siblings.

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?

'Use this when the user wants to create many QR codes or short links from a spreadsheet and needs the template' gives a clear triggering condition. It doesn't name the next-step alternatives (submit_batch) or state when not to use it, so it stops 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 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?