Riddle

questionBank_getItems

Read-onlyIdempotent

Lists the items (draft content) of a question bank, optionally filtered by search term, blockType, category or difficultyRange - the same filters the Creator's question bank grid offers. Also reads a built-in template from questionBank_templateList, which is how to preview a template's actual questions before deciding to duplicate it - pass page/pageSize there, a template can hold tens of thousands of items and is returned in full otherwise. Deliberately unlike questionBank_list: omitting page/pageSize here returns everything rather than defaulting to a page, since a bank you filled yourself is often small enough that "everything" is the right answer - an invalid page/pageSize (zero, negative, non-numeric, fractional, or a pageSize over 100) is rejected outright rather than silently clamped.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, starting at 1. Omit (with pageSize also omitted) to return every matching item at once - not what you want on a big bank or a template, which hold thousands of items; unlike questionBank_list, this tool never paginates on its own. Zero, negative, non-numeric or fractional is rejected, not rounded.
`search`	No	Search term to filter items by their column values (e.g. the question title or a choice).
`category`	No	Filter items to only this category.
`pageSize`	No	Items per page, only used together with page - given alone it is taken as page 1, not ignored (default: 50, max: 100). Same validation as page; over 100 is rejected, not clamped.
`blockType`	No	Filter items to only this block type (e.g. "SingleChoice").
`questionBankId`	Yes	The ID of the question bank to list items of - an own bank, or a built-in template from questionBank_templateList to preview its questions.
`difficultyRange`	No	Filter items to a difficulty range, as [min, max] (e.g. [1, 5]). Omit for no difficulty filter.

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses important non-obvious behaviors: omitting pagination returns everything, templates can return tens of thousands of items, and invalid page/pageSize values are rejected outright rather than clamped. This is exactly the kind of behavioral context annotations alone do not provide.

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 dense but every sentence earns its place: it front-loads the core purpose, then covers filtering, template preview, pagination behavior, and the contrast with questionBank_list. Despite its length, there is no filler and the structure makes the unusual pagination semantics easy to understand.

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 tool with seven parameters, no output schema, and tricky pagination rules, the description is fully sufficient for selection and correct invocation. It covers all filter options, the template use case, the safe pagination behavior, and the sibling distinction, leaving no major decision-relevant gap.

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 already documents all seven parameters in detail, so the baseline is high. The description adds useful cross-parameter context about how page/pageSize interact, when to pass them, and that the same filter values map to the Creator's question bank grid, but much of the per-parameter meaning already lives in 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 action (list the items/draft content of a question bank), names the available filters, and explicitly differentiates itself from questionBank_list by describing its different pagination behavior. It also covers the template-preview use case, making the tool's purpose and scope unmistakable.

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?

The description gives concrete guidance on when to use this tool: to list bank items, to filter with the same options as the Creator grid, and to preview built-in templates before duplicating them. It explicitly contrasts with questionBank_list and tells the caller when to pass page/pageSize and when to omit them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Riddle tools Inspect

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

A4.1/5.0

Disambiguation5/5

Each tool has a clear, unique purpose. The riddle_builder_* variants are distinct by Riddle type, questionBank_* and riddleTemplate_* cover separate objects, and stats_* differ by scope. No two tools appear to perform the same function.

Naming Consistency4/5

Naming is largely consistent with domain prefixes (riddle_, questionBank_, riddleTemplate_, stats_, project_, palette_, reference_). Minor deviations like riddle_account_list vs. riddle_list and whoami (no prefix) and riddle_get_embed_code vs. riddle_qr_code slightly break the pattern, but overall it is predictable.

Tool Count2/5

With 62 tools, the server is far beyond the typical 3-15 well-scoped range. While each tool is functional and the breadth reflects the platform's complexity, the sheer number makes it heavy and increases the cognitive load for an agent, suggesting over-granularity.

Completeness5/5

The tool set covers the full lifecycle: create (builder variants), read (get/list), update (builder_update, rename), delete, publish/unpublish, tagging, templates, question banks, stats, projects, palettes, and reference documentation. No obvious domain operation is missing.

Resources

Need Help?