riddle_move_check

shallow

com.riddle/creator · Verify this server

Checks, without changing anything, whether a set of Riddles can be moved and which projects they can be moved to - the same check riddle_move runs before it moves anything. Pass exactly the UUID/UUIDs you intend to hand to riddle_move, because the answer depends on the whole set: a Riddle that is connected to another one (a Form embedded into another Riddle as a form select, a Quiz reporting into a Leaderboard) can only be moved when everything it is connected to moves with it, so the same Riddle can be blocked on its own and movable as part of a larger call. Returns {canMoveAll, movable, blocked, addUUIDs, canMoveToPersonal, projects}: "blocked" names, per Riddle, "missingRiddles" (the exact connected Riddles that are not part of the set, each with uuid, title, type and relation: "dependent" for a Riddle reporting into it, "embedded" for a Riddle it embeds), "missingUUIDs" as the bare UUIDs to add, "connectedRiddles" as the unfiltered picture of everything it is connected to, "inaccessibleConnections" as the number of connected Riddles in projects you cannot access, "blockedByRiddlesInThisCall" as the Riddles of this very call that hold it back because they are blocked themselves, "resolveByAddingUUIDs" as what to add so THIS Riddle can move, and "resolvable" telling you whether adding UUIDs can fix it at all. Blocking travels along connections, so act on "resolveByAddingUUIDs" (or simply on the top-level "addUUIDs"), never on an empty "missingUUIDs": a Riddle whose connections are all in the set already has nothing of its own to add and is still blocked while the Riddle it is tied to is - "resolvable" is therefore shared by all Riddles that can only move together, and false only when one of them is connected to a Riddle you cannot reach at all. "addUUIDs" is the deduplicated union of every missingUUIDs - add it to UUIDs and check again, repeating until canMoveAll is true, because connections chain (a Quiz you add for one Leaderboard can report into a second one) - and "projects" is the intersection of the projects EVERY Riddle of the set can go to - a project you may lack the transfer permission in, or that does not support something one of the Riddles uses, is not in it. Use this before riddle_move whenever the Riddles were not all created by you, or to explain to the user why a move is not possible.

100.0/100

1 trials · measured 8 days ago

riddle_move_check scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.riddle/creator, measured 25 Aug 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
gated
Category
Content & media
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-08-25100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 1

Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.

Embed this score

Available for every tool, scored or not — not a verification perk. Always links back to this page.

Vouch score: riddle_move_check
[![Vouch score](https://vouch.tools/api/tools/a2bce63f-ad2a-4aec-876e-8ba056657c1e/badge.svg)](https://vouch.tools/tools/a2bce63f-ad2a-4aec-876e-8ba056657c1e)
riddle_move_check — Vouch