QRStuff MCP Server

Restore deleted QR code

restore_deleted_qrcode

Idempotent

Use this when the user says a QR code was deleted by mistake and wants it back. Needs the code ID or short-URL key. Restores it to their account.

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

Input Schema

Name	Required	Description	Default
`idqrcode`	No	ID of the deleted QR code. Required if shorturl_key is not given.
`shorturl_key`	No	Short-URL key of the deleted QR code. Required if idqrcode is not given.

Output Schema

Name	Required	Description	Default
`ok`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 30, 2026

addedInput schema / properties / idqrcode / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "integer"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / idqrcode / default
```
Previous value: -0New value: +null
```

changedInput schema / properties / idqrcode / description

Previous value: -"QR code ID to restore. Use if customer provides numerical ID."New value: +"ID of the deleted QR code. Required if shorturl_key is not given."

removedInput schema / properties / idqrcode / type
```
Removed value: -"integer"
```

addedInput schema / properties / shorturl_key / anyOf

Added value: +[
+  {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "default": null
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / shorturl_key / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / shorturl_key / description

Previous value: -"Short URL key (path without leading slash) for the QR code. Use if customer provides short URL."New value: +"Short-URL key of the deleted QR code. Required if idqrcode is not given."

removedInput schema / properties / shorturl_key / type
```
Removed value: -"string"
```

First observedOct 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description usefully adds that the code is restored 'to their account', clarifying the recovery semantics. It says nothing about entitlement/plan-slot constraints on restore, whether the original short-URL is reused, or what happens if the ID does not refer to a deleted code.

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, front-loaded with the invocation trigger, then the input requirement, then the effect. No filler and nothing that duplicates structured fields verbatim.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile for this simple two-param mutation. Trigger, required input, and post-condition are all present — nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real value by stating that an identifier is required ('Needs the code ID or short-URL key') — the schema has zero required parameters and would otherwise permit an empty call. It restates the either/or relationship between the two params without adding format detail.

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 pairs a specific verb ('Restores') with a specific resource ('QR code'), and the intent framing ('deleted by mistake and wants it back') makes the operation unambiguous. It implicitly separates itself from restore_deleted_project by resource, but never names that sibling, so it stops just short of full sibling differentiation.

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 says a QR code was deleted by mistake and wants it back' gives a concrete triggering condition rather than a vague 'manage QR codes' framing. It does not state exclusions or point to related tools (e.g. list_deleted_projects for locating the deleted item first), so there is no explicit when-not guidance.

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?