Skip to main content
Glama

Riddle Quiz Maker

by com.riddle
OverviewDiscussionsAdmin

riddle_move

Destructive

Moves one or many Riddles into another project or into the personal project - and, given no destination, reports whether it could instead of moving anything. Pass UUID for one Riddle or UUIDs (max 100) for several. CHECK MODE: leave projectId out (or pass dryRun: true alongside one) and NOTHING is changed - the call runs the very same validation a real move runs and answers {canMoveAll, movable, blocked, addUUIDs, canMoveToPersonal, projects}. Do this first whenever the Riddles were not all created by you, or to explain to a user why a move is impossible. MOVE MODE: pass projectId (a project/team ID from project_list, or the string "personal") and the Riddles move, answering {bulk, operation, summary, results} with the new project per Riddle. Unlike the other bulk tools this one is atomic - it validates the whole set first and moves nothing if any Riddle is rejected - because Riddles that reference each other (a Quiz and the Leaderboard it reports to, a Form embedded in another Riddle) can only move together. So pass exactly the set you intend to move: the same Riddle can be blocked on its own and movable inside a larger call. When something is blocked, act on the top-level "addUUIDs" (or a blocked entry's "resolveByAddingUUIDs"), add those to UUIDs and check again until canMoveAll is true - connections chain, and blocking travels along them, so never read an empty "missingUUIDs" as "this one is fine" or a blocked Riddle as having a problem of its own. A move drops project-specific ad blocks tied to the old project and updates the published version along with the draft, but it does not adopt the new project's design. Every field of the check answer, why "projects" can be shorter than project_list and when a blocker cannot be resolved at all: riddle://reference/concepts/move-restrictions. Only if the Riddle's origin.writableByThisKey is true (riddle_get, riddle_list): riddle://reference/concepts/access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
UUIDNoThe UUID of the single Riddle you want to move or check. Pass either this or UUIDs.
UUIDsNoSeveral Riddles to move or check at once, as Riddle UUID strings, e.g. ["6FA740EW", "OllsevHa"] (max 100). Pass either this or UUID. For a move, this must be the complete set of Riddles that have to move together.
dryRunNotrue runs the movability check against the given projectId and changes nothing. Pointless without projectId, which already only checks.
projectIdNoWhere to move the Riddles: the project (team) ID to move them into, as returned by project_list, or the string "personal" for your personal project. There is no default destination - omit this and nothing is moved, the call reports the read-only movability check instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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"
+    ]
+  }
+]
    • changedInput schema / properties / UUID / description
      Previous value: -"The UUID of the single Riddle you want to move. Pass either this or UUIDs."New value: +"The UUID of the single Riddle you want to move or check. Pass either this or 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
-}
    • changedInput schema / properties / UUIDs / description
      Previous value: -"Several Riddles to move at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID."New value: +"Several Riddles to move or check at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID. For a move, this must be the complete set of Riddles that have to move together."
    • 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 runs the movability check against the given projectId and changes nothing. Pointless without projectId, which already only checks.",
+  "type": "boolean"
+}
    • addedInput schema / properties / projectId / anyOf
      Added value: +[
+  {
+    "description": "A project (team) ID from project_list.",
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "const": "personal",
+    "description": "Move the Riddles into the personal project.",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / projectId / description
      Previous value: -"The project (team) ID to move the Riddles into, as returned by project_list. Omit or pass null to move them to your personal project instead."New value: +"Where to move the Riddles: the project (team) ID to move them into, as returned by project_list, or the string \"personal\" for your personal project. There is no default destination - omit this and nothing is moved, the call reports the read-only movability check instead."
    • changedInput schema / properties / projectId / type
      Previous value: -[
-  "null",
-  "integer"
-]New value: +[
+  "null",
+  "integer",
+  "string"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds substantial behavioral detail beyond them: atomic validation of the whole set before any move, dropping project-specific ad blocks tied to the old project, updating the published version alongside the draft, not adopting the new project's design, and warning that empty missingUUIDs does not mean a Riddle is fine. No contradiction with annotations.

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?

It is front-loaded with the mode distinction and every sentence carries actionable information, but it is unusually long and somewhat repetitive — dryRun's redundancy is explained both in the schema and the description, and the reference pointers add length. Dense but not wasteful.

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 no output schema, the description compensates by naming both return shapes ({canMoveAll, movable, blocked, addUUIDs, canMoveToPersonal, projects} for check; {bulk, operation, summary, results} for move) and routing to two reference resources for the unresolved edge cases, leaving nothing an agent needs to call it correctly unspecified.

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 description coverage is already 100%, so the schema documents all four parameters. The description still adds meaning beyond it by explaining the UUID/UUIDs exclusivity intent ('pass exactly the set you intend to move'), the max-100 bulk semantics, when roomId-like destinations come from project_list, and that dryRun is pointless without projectId.

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 opens with a specific verb+resource+scope: it moves one or many Riddles into another project or the personal project, and with no destination performs a check instead. This dual mode is stated up front and is easily distinguished from siblings like riddle_list, riddle_get, and riddle_delete.

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 explicitly prescribes when to use check mode vs move mode ('Do this first whenever the Riddles were not all created by you, or to explain to a user why a move is impossible'), how to resolve blocked states iteratively, and gates usage on origin.writableByThisKey with pointer to the access reference.

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