Riddle Quiz Maker

riddle_template_use

Creates a new Riddle from a template as an unchanged copy of it - content, settings and design preset - recorded as a copy of the template's Riddle (riddle_get reports it as context.duplicated). Use this whenever the template is what you want; to adapt it first, read it with riddle_template_get and build the edited configuration with riddle_builder_create instead. The new Riddle is a DRAFT - riddle_publish makes it live - except that Riddles the template embeds or that depend on it (a Form, a Leaderboard) are copied and published right away, and so is the new Riddle when one of them depends on it. Returns it in the standard build-configuration envelope, and takes riddle_get's "omit" to leave sections of it out. Requires the template-use permission plus Riddle-create in the target project.

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": {
      "id": "<id>"
    },
    "name": "riddle_template_use"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The ID of the template to create a Riddle from, as returned by riddle_template_list or riddle_template_public_list.
`omit`	No	Same "omit" parameter as riddle_get's, applied to the returned envelope (see riddle_get for the full description): sections of it to leave out, "published" being the one that still moves a copy of a template materially. The per-block default maps are not in this response at all - they are opt-in through riddle_get/riddle_template_get and this tool has no such parameter.
`title`	No	Title for the new Riddle. Omit to keep the template's own title.
`projectId`	No	The project (team) ID to create the Riddle in, as returned by project_list. Omit to use the project the API key is scoped to (your personal project for a user API key).

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the publish state of the result (DRAFT, with the exception that embedded/dependent Riddles such as a Form or Leaderboard are copied and published immediately), the required permissions ('template-use plus Riddle-create in the target project'), and that riddle_get reports it as context.duplicated. Minor gap: no mention of what happens if the template is deleted or whether a copy can be made repeatedly beyond idempotentHint=false.

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?

Front-loaded with the action and the alternative, then the draft/publish nuance, return shape and permissions. It is a single dense paragraph and the embed/dependency exception is slightly convoluted ('and so is the new Riddle when one of them depends on it'), but no sentence is filler.

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 describing the return ('the standard build-configuration envelope') and the omit trimming. It also covers the mutation's side effects and auth requirements, so an agent has everything needed to invoke it correctly.

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%, so the schema already documents id, omit, title and projectId in detail; the baseline of 3 applies. The description only restates the omit parameter ('takes riddle_get's "omit" to leave sections of it out') without adding syntax or defaults beyond the schema, and never mentions title or 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?

States a specific verb and resource ('Creates a new Riddle from a template') plus the exact semantics of the operation ('an unchanged copy of it - content, settings and design preset'). It also distinguishes the outcome from the sibling that produces an edited Riddle, so an agent can tell riddle_template_use from riddle_builder_create without opening either schema.

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?

Gives an explicit selection rule: 'Use this whenever the template is what you want; to adapt it first, read it with riddle_template_get and build the edited configuration with riddle_builder_create instead.' Both the use case and the alternative path with its prerequisite step are named.

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?