Riddle Quiz Maker

question_bank_list

Read-onlyIdempotent

Lists question banks. Scope "own" (the default) lists the banks of a project - the same ones the Creator shows; pass a projectId to look into another project, omit it for the project the API key is scoped to (your personal ones on a user API key). Paginated {items, page, pageSize, total, hasMore}. Scope "templates" lists the built-in starter banks instead - pre-filled banks anyone can copy with question_bank_duplicate to get real content immediately instead of starting empty. It takes riddleType and nothing else (a handful of them, nothing to page or search) and answers with id, title, PUBLISHED "itemCount", DRAFT "draftItemCount", which blockTypes those items are (null when that cannot be told yet) and a few example categories out of "categoryCount". A template that was never published reports "itemCount": 0 however many questions it holds - judge its real size by "draftItemCount", the number a duplicate would give you, and read the chosen id with question_bank_get and question_bank_get_items before duplicating. Every write here rejects a template id: a template is only ever changed through a copy of it.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "question_bank_list"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1). Scope "own" only.
`tags`	No	Filter by tag IDs (array of integers), as returned by riddle_tag_list. Omit to ignore tags. Scope "own" only.
`scope`	No	What to list: "own" (default) for the question banks of a project, "templates" for the built-in starter banks anyone can duplicate.
`search`	No	Search term to filter banks by title. Scope "own" only.
`sortBy`	No	Sort field: "createdAt" or "modifiedAt". Defaults to "createdAt". Scope "own" only.
`pageSize`	No	Items per page (default: 12, max: 50). Scope "own" only.
`projectId`	No	The project (team) ID whose banks you want, as returned by project_list. Omit for the banks of the project the API key is scoped to (your personal ones on a user API key). Scope "own" only.
`sortOrder`	No	Sort direction: "ASC" or "DESC". Defaults to "DESC". Scope "own" only.
`riddleType`	No	Filter by Riddle type ("Quiz" or "Poll"). Omit to list banks of every type. Applies to both scopes.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Although annotations already declare a safe read-only and idempotent operation, the description adds important behavior: pagination shape, template-specific itemCount versus draftItemCount semantics, and the rule that every write rejects a template id. Those details materially affect how an agent interprets and uses the results.

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 front-loaded with the core distinction between own and template scopes, and most sentences carry useful caveats. It is dense and somewhat long for a list tool, with some repetition of schema-level scope and projectId behavior, but not enough to obscure the key guidance.

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?

There is no output schema, so the description must explain return shape; it does so by naming pagination fields, template-specific fields, null blockTypes behavior, and category examples. It also covers the critical template caveat and pre-duplication verification flow, making it complete for correct invocation.

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 coverage is 100%, so parameter basics are already documented. The description adds cross-parameter context, especially that templates take only riddleType and are not pageable or searchable, but it largely restates the scope and projectId semantics from the schema.

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 states a specific verb and resource ("Lists question banks") and immediately distinguishes the two listing scopes, own project banks versus built-in templates. It also names the related duplication and read tools, so an agent can understand its role without opening sibling schemas.

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?

It gives explicit selection rules: use scope "own" for a project's banks, pass projectId to inspect another project, omit it for the key-scoped project, and use scope "templates" for starter banks. It also routes the agent to question_bank_get, question_bank_get_items, and question_bank_duplicate before copying a template.

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?