QRStuff MCP Server

Create restaurant menu QR code

create_menumaker_qrcode

Use this when the user wants a digital menu for a restaurant, cafe or bar opened by QR code. Creates a menu in QRStuff's menu builder and a dynamic QR code for it, and returns the code and a link to add items. To use an existing PDF menu, use generate_qr_code with type PDF instead.

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": {
      "menu_name": "<menu_name>"
    },
    "name": "create_menumaker_qrcode"
  }
}

Input Schema

Name	Required	Description	Default
`qr_name`	No	Optional name for the QR code in the dashboard.	Menu QR Code
`menu_name`	Yes	Name of the menu, for example the restaurant name.

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 cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false). The description adds value beyond them by disclosing where the object is created (QRStuff menu builder) and what the caller gets back (code plus a link to add items). It stops short of saying whether repeated calls create duplicate menus or how to undo, so not a 5.

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 sentences, zero padding, with the primary use case front-loaded and the alternative routing placed second where it does not compete with the main instruction.

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 two-parameter creation tool with an output schema, annotation coverage of the safety hints, and an explicit sibling alternative, nothing an agent needs in order 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 description coverage is 100% and both parameters are documented there, including the 'restaurant name' example for menu_name. The description adds no syntax, format, or constraint detail beyond the schema, so the 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?

States a specific verb and resource: creates a menu in QRStuff's menu builder plus a dynamic QR code, and returns the code and an item-adding link. It also explicitly distinguishes itself from generate_qr_code, so an agent can separate it from the many other create_* siblings.

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 a clear trigger ('user wants a digital menu for a restaurant, cafe or bar opened by QR code') and names the alternative with its selection condition ('To use an existing PDF menu, use `generate_qr_code` with type PDF instead'). No inference required.

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?