Riddle Quiz Maker

question_bank_manage

Everything that acts on a question bank as a whole, by "action" - the items themselves are question_bank_item, and the two calls that only destroy are question_bank_delete and question_bank_discard_changes. A public template id is accepted for "duplicate" only and rejected by every other action. "rename" sets the title and "updateNotes" replaces the plain-text maintainer notes (never shown to participants): both are metadata rather than DRAFT content, so they take effect immediately AND permanently, are unaffected by publishing or discarding and never count as an unpublished change. "publish" makes every item's draft content its published content - what a QuestionBank block actually draws at view time - and is when a pending item delete is finally purged; a bank with unpublished changes still works in a block, it just draws its last published state. "duplicate" copies the bank and all of its items into a new independent bank (editing one never affects the other) in projectId or the key's project, and is the way to change a public template. Needs full access: riddle://reference/concepts/access.

Input Schema

TableJSON Schema

Name	Required	Description
`notes`	No	Plain-text notes for this bank, e.g. sourcing/curation instructions - replaces any existing notes. Required for "updateNotes", rejected for every other action.
`title`	No	The new title for "rename", or the title of the copy for "duplicate". Required for both, rejected for every other action.
`action`	Yes	What to do with the bank: "rename" (takes title), "updateNotes" (takes notes), "duplicate" (takes title and optionally projectId) or "publish" (no further parameters).
`projectId`	No	The project (team) ID the copy should land in, as returned by project_list. Only for "duplicate", where omitting it uses the project the API key is scoped to.
`questionBankId`	Yes	The ID of the question bank to act on.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 2, 2026

TDQS

A4/5.0

Behavior1/5

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

Annotations declare destructiveHint=false, but the description states that publish 'is when a pending item delete is finally purged,' which is a destructive effect on items. This directly contradicts the non-destructive annotation, so per the rules the score is 1.

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?

The description is dense and long, but it is front-loaded with overall scope and then moves through action semantics. The length is justified by the multi-action complexity, though it reads as a wall of text rather than tightly concise prose.

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?

Given the multi-action management surface, the description covers action effects, side effects, access requirements, and sibling routing. No output schema exists, and return values are not needed for correct invocation, so this is complete enough.

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 100%, so the baseline is 3. The description adds useful constraints beyond the schema, notably that a public template id is accepted only for duplicate and rejected by every other action, and clarifies metadata vs DRAFT effects for rename/updateNotes.

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 the tool acts on a question bank as a whole via an action parameter, explicitly distinguishes item-level operations (question_bank_item) and destroy-only calls (question_bank_delete, question_bank_discard_changes). Specific verb+resource and clear sibling differentiation.

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?

Names alternative tools and when to use them, e.g. items are handled by question_bank_item and destroy-only actions by question_bank_delete/question_bank_discard_changes. Also gives action-specific conditions such as public template id accepted only for duplicate and rejected elsewhere.

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?