QRStuff MCP Server

Manage QR code variants

manage_qrcode_variants

DestructiveIdempotent

Use this when the user wants one dynamic QR code to open different destinations depending on conditions such as the scanner's device (Smart Rules). Saves up to 10 variants for that code. Call get_qrcode_variant_rules first.

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": {
      "idqrcode": "<idqrcode>",
      "variants": "<variants>"
    },
    "name": "manage_qrcode_variants"
  }
}

Input Schema

Name	Required	Description	Default
`idqrcode`	Yes	Dynamic QR code ID from `list_qrcodes`. Never guess an ID.
`variants`	Yes	Up to 10 variants, each with a name, optional position, rules (if.all or if.any conditions) and the destination to open. Use the fields and operators from `get_qrcode_variant_rules`.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, and the description is consistent with them. However, the most important behavior for a destructive mutation — whether saving variants replaces/overwrites existing variants and whether that is reversible — is never stated; only the 10-variant cap is added.

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?

Three short sentences, front-loaded with the use case before the cap and the prerequisite call. No filler; the only slight redundancy is restating the 10-variant limit that the schema also carries.

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 a 100% documented schema, an output schema present, and annotations covering the safety profile, the description supplies the remaining workflow context an agent needs (Smart Rules purpose, prerequisite lookup call). The overwrite semantics on save would be the final piece to make it fully complete.

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 already documents both the idqrcode provenance ('Never guess an ID') and the variants structure including the 10-item cap and rule fields. The description adds no syntax or format information beyond what the schema provides, so the baseline 3 applies.

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?

The description names the concrete effect: saving up to 10 Smart Rules variants so one dynamic QR code routes scanners to different destinations. That is far more specific than the vague 'manage' verb in the name, though it doesn't distinguish this from sibling update_qrcode_variant_status, which also touches variants.

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?

It states the trigger clearly ('when the user wants one dynamic QR code to open different destinations depending on conditions') and gives an explicit prerequisite workflow step: 'Call `get_qrcode_variant_rules` first.' It stops short of naming the alternative for toggling an existing variant's status.

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?