QRStuff MCP Server

Submit batch

submit_batch

Use this when the user has filled in the bulk spreadsheet and wants the codes made. Starts a background job that creates one QR code or short link per row; check it with get_batch_status. Upload the XLSX with upload_file first (and a ZIP for file-based types).

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": {
      "batch_file_id": "<batch_file_id>",
      "batch_name": "<batch_name>"
    },
    "name": "submit_batch"
  }
}

Input Schema

Name	Required	Description	Default
`idproject`	No	Optional project ID from `list_projects` to file it in.
`batch_name`	Yes	Name for this bulk job.
`batch_type`	No	qrcode for QR codes or short_link for short links.	qrcode
`zip_file_id`	No	`idfs_file` of a ZIP with the files, from `upload_file`. Only for file-based types.
`batch_file_id`	Yes	`idfs_file` of the filled XLSX from `upload_file`.

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=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds genuinely non-structured context: the operation is asynchronous, it spawns a background job, and it produces one output per spreadsheet row, which tells the agent not to expect immediate results. It stops short of warning about duplicate submissions creating duplicate batches or any quota limits.

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 tight sentences: trigger first, behavior second, prerequisites and follow-up last. Every sentence carries distinct information and none is padding.

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 no explanation, and annotations cover the safety profile. The description supplies the remaining essentials an agent needs: the async model, the prerequisite upload step, and the status-check tool.

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 all five parameters are already documented, including the enum for batch_type and the idfs_file provenance for the file IDs. The description's mention of the XLSX and ZIP largely restates what the schema says, adding only the framing that file-based types need the ZIP.

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 action and outcome: starts a background bulk job that creates one QR code or short link per row. This clearly distinguishes it from the single-item siblings like create_short_link or generate_qr_code, and from the read-side get_batch_status.

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?

Gives an explicit trigger condition ("when the user has filled in the bulk spreadsheet and wants the codes made"), names the follow-up tool get_batch_status, and states the prerequisite of uploading the XLSX (plus a ZIP for file-based types) via upload_file. An agent has a complete call sequence 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?