Riddle Quiz Maker

riddle_template_create

Stores an existing Riddle as a template of its project (or of the user, for a personal Riddle), so new Riddles can be created from it with riddle_template_use. The template is a copy taken at this moment - the Riddle keeps living its own life and later changes to it do not reach the template. It copies what the Riddle currently has stored, published or not. Returns the created template: {id, title, type, category, isPublic, isQuickCreate, blocksCount, image, icon, createdAt, riddle}. Requires the template-create permission in the Riddle's project. Without full access only for a Riddle whose origin.writableByThisKey is true: riddle://reference/concepts/access.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "UUID": "<UUID>"
    },
    "name": "riddle_template_create"
  }
}

Input Schema

Name	Required	Description
`UUID`	Yes	The UUID of the Riddle to store as a template, e.g. "6FA740EW".
`title`	No	Title for the template. Omit to keep the Riddle's own title.
`iconMediaId`	No	Same, for the "icon".
`coverMediaId`	No	Media library image to show as the template's "image" from the Riddle's project (see riddle_template_update). Omit for the Riddle's own cover.
`isQuickCreate`	No	Whether the template also shows up in the Creator's "quick create" list, i.e. among the starting points offered when creating a new Riddle. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedInput schema / properties / coverMediaId / description

Previous value: -"Media library image to show as the template's \"image\" (see riddle_template_update). Omit for the Riddle's own cover."New value: +"Media library image to show as the template's \"image\" from the Riddle's project (see riddle_template_update). Omit for the Riddle's own cover."

Changed2 schema fields changedOct 6, 2026

addedInput schema / properties / coverMediaId

Added value: +{
+  "default": null,
+  "description": "Media library image to show as the template's \"image\" (see riddle_template_update). Omit for the Riddle's own cover.",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

addedInput schema / properties / iconMediaId

Added value: +{
+  "default": null,
+  "description": "Same, for the \"icon\".",
+  "type": [
+    "null",
+    "integer"
+  ]
+}

AddedSep 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it clarifies snapshot semantics ('The template is a copy taken at this moment... later changes to it do not reach the template'), states copy scope ('copies what the Riddle currently has stored, published or not'), describes permission requirements, and enumerates the return object's fields. These details are not present in the annotations, which only declare readOnlyHint=false, destructiveHint=false, etc.

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?

The description is front-loaded with the core purpose and follows with tightly relevant behavioral, permission, and return-value details. Every sentence adds value, and there is no repetition or filler; even the reference link to access concepts is purposeful.

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?

Although there is no output schema, the description explicitly lists return fields ('{id, title, type, category, isPublic, isQuickCreate, blocksCount, image, icon, createdAt, riddle}'). Combined with rich annotations and a fully described input schema, the definition covers everything an agent needs to call the tool correctly.

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?

With 100% schema description coverage, the schema already documents all five parameters. The description still adds meaningful semantics by clarifying the scope of the copy triggered by the UUID parameter ('copies what the Riddle currently has stored, published or not') and by noting that omitting fields preserves the Riddle's own values, though it does not individually explain each parameter.

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 first sentence states a specific verb and resource: 'Stores an existing Riddle as a template of its project (or of the user, for a personal Riddle)'. It explicitly names the sibling tool riddle_template_use as the consumer of the created template, so an agent can distinguish creation from usage without opening any schema.

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?

The description gives clear usage context: it explains that the template enables creation via riddle_template_use, and it states permission prerequisites ('Requires the template-create permission') plus an access caveat for non-full-access callers. It does not explicitly list when-not-to-use cases or name an alternative creation pathway, which keeps it at 4 rather than 5.

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 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?