Skip to main content
Glama

Riddle Quiz Maker

by com.riddle

questionBank_duplicate

Duplicates a question bank and every one of its items into a new, independent bank - the items are copies, editing one bank never affects the other. Works on your own banks and on templates from questionBank_templateList. The copy lands in the project given as projectId, or in the project the API key is scoped to when none is named; a bank can only be referenced from Riddles of its own project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesThe title for the new, duplicated bank.
projectIdNoThe project (team) ID the copy should land in, as returned by project_list. Omit for the project the API key is scoped to (your personal space on a user API key).
questionBankIdYesThe ID of the question bank to duplicate - an existing bank or a template from questionBank_templateList.

TDQS

A4.7/5.0
Behavior5/5

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

With only idempotentHint: false in annotations, the description carries the burden of behavioral disclosure. It clearly states that copies are independent, how projectId defaults work, and the constraint regarding referencing from Riddles. This goes beyond the schema and gives the agent full awareness of what happens during duplication.

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 three sentences long and each sentence adds critical information without fluff. It fronts the primary action, then explains independence, then covers project placement and scoping rules. Every phrase earns its place, making it efficient and well-structured.

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?

For a duplication tool with no output schema, the description covers the essential aspects: what is copied, the independence guarantee, accepted inputs (own banks and templates), output project selection, and a usage constraint. This is comprehensive given the moderate complexity and the fact that no return format needs explanation.

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?

The input schema has detailed descriptions for all three parameters, covering 100% of them. The description adds value by clarifying that the projectId defaults to the API key's scoped project and that questionBankId can reference templates. While the schema already explains the basics, the description reinforces the copying semantics and project fallback.

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 description clearly states the tool duplicates a question bank and its items into an independent copy, using specific verbs and context about copies being independent. It differentiates from sibling tools like questionBank_create (creates anew) and questionBank_templateList (lists templates) by specifying it works on banks and templates. The distinction between copying and referencing is precisely articulated.

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 explains when to use the tool (to duplicate banks or templates) and provides context about project placement behavior. It mentions that templates from questionBank_templateList are supported and that the bank's project scoping affects Riddle references. However, it doesn't explicitly state what the tool does NOT do or when to prefer an alternative, but the guidance is strong.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Tools are largely distinct by name and detailed descriptions, with clear prefixes (riddle_builder_*, questionBank_*, stats_*). Some potential confusion exists among the stats tools (stats_fetch vs stats_overview_fetch vs breakdowns) but descriptions clarify their different scopes. Overall, an agent can usually pick the right tool.

Naming Consistency4/5

Naming follows a predictable prefix+verb pattern within each domain (e.g., riddle_builder_quiz, riddle_builder_poll; riddle_get, riddle_publish). Minor inconsistencies exist, like the camelCase 'questionBank' and 'riddleTemplate' prefixes vs snake_case elsewhere, and 'stats_overview_fetch' ordering, but these are not chaotic and remain readable.

Tool Count1/5

With 62 tools, this far exceeds the recommended 3-15 range and even the 25+ threshold. While the server covers a broad domain, the extreme number overwhelms and makes tool selection harder, fitting the 'extreme mismatch' criterion for 50+ tools.

Completeness5/5

The tool surface is exceptionally comprehensive, covering creation, reading, updating, deleting, publishing, unpublishing, moving, tagging, template management, question banks, palettes, and various stats breakdowns. There are no obvious gaps in the lifecycle of managing interactive content, and all apparent operations are supported.

Resources