Skip to main content
Glama
Sign In

Riddle Quiz Maker

by com.riddle
OverviewDiscussionsAdmin

riddle_delete

Destructive

Deletes one or many Riddles. Pass UUID for one, or UUIDs (max 100) to clean up several at once - e.g. everything riddle_list returned with origin: "api". A bulk delete is not atomic and never gives up early: a Riddle that cannot be deleted is that entry's "error" and every other Riddle is still deleted (riddle://reference/concepts/bulk). A Riddle another item of the same batch still references (a Leaderboard's connected Quiz/Predictor/Minigame, a FormSelect's Form) is retried once after the rest of the batch, so the order of the list does not matter; only a failure that survives the retry is reported. DRY RUN: pass dryRun: true and NOTHING is deleted - the call runs the same validation a real delete runs and answers {dryRun, deletable, summary, items, addUUIDs} per Riddle. Do this first whenever the set was not created by you; then act on "addUUIDs" to delete the referencing Riddles along with their targets. Every field, the batch effect and which blockers no addition to the call can lift: riddle://reference/concepts/bulk. Only if the Riddle's origin.writableByThisKey is true (riddle_get, riddle_list): riddle://reference/concepts/access.

Input Schema

NameRequiredDescriptionDefault
UUIDNoThe UUID of the single Riddle you want to delete. Pass either this or UUIDs.
UUIDsNoSeveral Riddles to delete at once, as Riddle UUID strings, e.g. ["6FA740EW", "OllsevHa"] (max 100). Pass either this or UUID.
dryRunNotrue reports whether each Riddle could be deleted and deletes nothing. Works for one UUID and for UUIDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / UUID / description
      Previous value: -"The UUID of the single Riddle you want to delete. Pass either this or UUIDs. Only Riddles created via the Riddle Builder tools or generated by the Riddle AI can be deleted."New value: +"The UUID of the single Riddle you want to delete. Pass either this or UUIDs."
    • changedInput schema / properties / UUIDs / description
      Previous value: -"Several Riddles to delete at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID. Same restriction as UUID: each one must have been created via the Riddle Builder or generated by the Riddle AI."New value: +"Several Riddles to delete at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID."
  2. Changed6 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "properties": {
+      "UUID": {
+        "not": {
+          "type": "null"
+        }
+      },
+      "UUIDs": {
+        "const": null
+      }
+    },
+    "required": [
+      "UUID"
+    ]
+  },
+  {
+    "properties": {
+      "UUID": {
+        "const": null
+      },
+      "UUIDs": {
+        "not": {
+          "type": "null"
+        }
+      }
+    },
+    "required": [
+      "UUIDs"
+    ]
+  }
+]
    • removedInput schema / properties / UUIDs / definition
      Removed value: -{
-  "items": {
-    "pattern": "^[A-Za-z0-9]{4,32}$",
-    "type": "string"
-  },
-  "maxItems": 100,
-  "minItems": 1,
-  "type": "array",
-  "uniqueItems": true
-}
    • addedInput schema / properties / UUIDs / items
      Added value: +{
+  "pattern": "^\\s*[A-Za-z0-9]{4,32}\\s*$",
+  "type": "string"
+}
    • addedInput schema / properties / UUIDs / maxItems
      Added value: +100
    • addedInput schema / properties / UUIDs / minItems
      Added value: +1
    • addedInput schema / properties / dryRun
      Added value: +{
+  "default": false,
+  "description": "true reports whether each Riddle could be deleted and deletes nothing. Works for one UUID and for UUIDs.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive annotation, it discloses nuanced behavior: bulk delete is non-atomic, does not stop early, retries dependent Riddles once, and reports per-entry errors. It also explains dryRun validation and the shape of the dry-run response, which is valuable behavioral context for a destructive tool.

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?

The description is dense and front-loads the key deletion and dry-run guidance. It is longer than typical but justified by the complex bulk and retry semantics, though some reference-link phrasing could be tightened.

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?

It covers most behavior an agent needs for a destructive batch delete, including atomicity, retries, per-item errors, dry-run behavior, and access conditions. It does not describe the normal successful delete response, but the annotations and dry-run detail reduce that gap.

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 schema already documents UUID, UUIDs, and dryRun. The description adds useful meaning by clarifying the either/or relationship, the 100-item limit, and especially the dryRun result fields and validation semantics.

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?

The description states a specific verb and resource: deletes one or many Riddles. It clearly distinguishes UUID single deletion from UUIDs bulk deletion and references sibling tools like riddle_list and riddle_get for context.

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?

It gives explicit when-to-use guidance: pass UUID for one, UUIDs for several, and dryRun first whenever the set was not created by you. It also names riddle_list as a source for the UUIDs to bulk-clean and explains the writableByThisKey access condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Riddle Quiz Maker toolsInspect
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