Skip to main content
Glama

Riddle

by com.riddle
OverviewDiscussionsAdmin

riddle_publish

Destructive

Publishes one or many Riddles, or takes them off the web again with publish: false - unpublishing is this tool, there is no separate unpublish tool. A published Riddle is live at https://www.riddle.com/view/[RIDDLEID]. With UUID the response is the riddle_get envelope with the new state under "context.published" ("omit" shrinks it the same way); with UUIDs (max 100) it is the bulk envelope, one compact entry per Riddle instead of a build configuration - not atomic and never giving up early, so a Riddle that cannot be (un)published is reported as that entry's "error" while the rest still go through (riddle://reference/concepts/bulk). PUBLISHING: a refusal is error "RIDDLE_PUBLISH_VALIDATE" carrying "validationErrors", one {message, code} per reason ("MIN_ONE_BLOCK", "MIN_ONE_RESULT", "REDIRECT_RESULT_WITHOUT_URL", "LOGIC_DEAD_ENDS", ...) - fix them all and publish again. Non-blocking findings arrive as "validationWarnings" on a FAILED and on a SUCCESSFUL publish alike (the Riddle is live either way): report them, do not retry. Only a publish produces either list - riddle_builder_validate dry-runs a build configuration, not a publish. UNPUBLISHING: a LIVE Leaderboard with active Riddle connections is refused ("RIDDLE_UNPUBLISH", same list naming what is in the way) - riddle_delete it instead, which is always allowed and cleans up the connected Riddles. Unpublishing a Riddle that is not live is a no-op that says so in a "message" - read it before reporting a Riddle as taken offline, because "context.published.at" is null whether it was never published or already offline. Codes and the draft-vs-live model: riddle://reference/concepts/publish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
UUIDNoThe UUID of the single Riddle you want to publish or unpublish. Pass either this or UUIDs.
omitNoSame "omit" parameter as riddle_get's, applied to the single-UUID response envelope (see riddle_get for the full description). Has no effect on the bulk (UUIDs) response, which never carries a build configuration to begin with.
UUIDsNoSeveral Riddles to publish or unpublish at once, as Riddle UUID strings, e.g. ["6FA740EW", "OllsevHa"] (max 100). Pass either this or UUID.
publishNotrue (the default) publishes the Riddles, false takes them off the web again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 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 publish. Pass either this or UUIDs."New value: +"The UUID of the single Riddle you want to publish or unpublish. 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 publish at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID."New value: +"Several Riddles to publish or unpublish at once, as Riddle UUID strings, e.g. [\"6FA740EW\", \"OllsevHa\"] (max 100). Pass either this or UUID."
    • 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
    • changedInput schema / properties / omit / items / enum
      Previous value: -[
-  "build",
-  "warnings",
-  "nextBlockId",
-  "published",
-  "context",
-  "build.omittedDefaults"
-]New value: +[
+  "build",
+  "warnings",
+  "nextBlockId",
+  "published",
+  "context"
+]
    • addedInput schema / properties / publish
      Added value: +{
+  "default": true,
+  "description": "true (the default) publishes the Riddles, false takes them off the web again.",
+  "type": "boolean"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes far beyond the sparse annotations (openWorldHint=false, idempotentHint=false, destructiveHint=true) by disclosing non-atomic bulk behavior ('not atomic and never giving up early... while the rest still go through'), the validation-error envelope, the no-op semantics of unpublishing a non-live Riddle, and the trap that 'context.published.at' is null whether it was never published or already offline. This is exactly the state-change nuance an agent needs before invoking a destructiveHint tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and every sentence carries real content, but the body is one dense run-on paragraph with semicolons, dashes, parenthetical asides, and a garbled validation-code list ('REDIRECT_RESULT_WITHOUT_URL' apparent duplication). The material would be far more scannable as short bullets or separate sentences.

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 no output schema, the description correctly carries the burden of explaining response shapes for both modes, partial failure, refusal codes, and the no-op edge case, and points to riddle://reference/concepts/publish and /bulk for the rest. Minor gaps remain: the bulk 'compact entry' fields are unspecified and auth expectations are never mentioned, but the reference links largely close the gap.

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% for all four parameters, so the baseline is 3; the schema already explains UUID/UUIDs exclusivity, maxItems 100, the publish boolean, and omit. The description adds modest value by mapping each parameter to its response envelope (single vs bulk) and noting omit has no effect on the bulk response, but it does not need to compensate for any schema gap.

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?

Opens with a specific verb and resource: 'Publishes one or many Riddles, or takes them off the web again with publish: false', and immediately draws the boundary that 'unpublishing is this tool, there is no separate unpublish tool.' This states both the action and its scope while distinguishing it from any sibling that might handle removal, so an agent cannot confuse it with riddle_delete or riddle_get.

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?

Gives clear context for the two invocation modes (single UUID vs bulk UUIDs max 100), the publish:false unpublish route, and when the tool will refuse (RIDDLE_PUBLISH_VALIDATE) or no-op (unpublishing a non-live Riddle). It does not, however, name sibling alternatives such as riddle_delete for permanent removal or riddle_builder_update for editing before publishing, so the when-not-to-use guidance is incomplete.

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

All Riddle 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