Riddle

questionBank_list

Read-onlyIdempotent

Lists the question banks of a project - the same banks the Creator's question bank list shows; pass a projectId to look into another project, omitting it lists the banks of the project the API key is scoped to (the personal ones for a user API key). Always paginated - page defaults to 1 and pageSize to 12 even when both are omitted, unlike questionBank_getItems which returns everything by default; a bank list can be large enough that "everything" is never the right default here. An invalid page/pageSize (zero, negative, non-numeric, fractional, or a pageSize over 50) is rejected outright rather than silently clamped. Use questionBank_templateList instead for the built-in starter banks.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (default: 1). Always applies, even when page and pageSize are both omitted: unlike questionBank_getItems, this never returns every bank at once. Zero, negative, non-numeric or fractional is rejected, not rounded.
`tags`	No	Filter by tag IDs (array of integers), as returned by questionBank_tagList. Omit to ignore tags.
`search`	No	Search term to filter banks by title.
`sortBy`	No	Sort field: "createdAt" or "modifiedAt". Defaults to "createdAt".
`pageSize`	No	Items per page (default: 12, max: 50). Same validation as page; over 50 is rejected, not clamped.
`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).
`sortOrder`	No	Sort direction: "ASC" or "DESC". Defaults to "DESC".
`riddleType`	No	Filter by Riddle type ("Quiz" or "Poll"). Omit to list banks of every type.

TDQS

A4.9/5.0

Behavior5/5

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

The description adds behavioral context beyond the readOnly/idempotent annotations: pagination always applies with defaults of page=1 and pageSize=12, invalid page/pageSize values are rejected rather than clamped, and pageSize over 50 is rejected. It also explains the scoping behavior of projectId, which annotations do not convey.

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, tightly packed with essential information: purpose, pagination behavior, validation rules, and alternatives. Every sentence earns its place, and the most important info is front-loaded.

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 8 optional parameters, no output schema, and good annotations, the description covers all key usage aspects: project scoping, pagination defaults, validation edge cases, and when to choose sibling tools. It is complete for a list operation with these structured fields.

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 baseline is 3. The description adds semantic value by explaining the 'always paginated' rationale, the projectId scoping behavior ('the same banks the Creator's question bank list shows'), and the cross-tool comparison with questionBank_getItems, which enriches understanding beyond the schema alone.

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+resource: 'Lists the question banks of a project,' and distinguishes it from siblings by explicitly contrasting questionBank_getItems and questionBank_templateList. It also clarifies the project scoping semantics, making the tool's purpose unambiguous.

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?

Provides explicit when-to-use guidance: pass projectId for another project, omit for the API key's scoped project; use questionBank_templateList for built-in starter banks; and contrasts with questionBank_getItems which returns everything by default. This gives clear alternatives and exclusions.

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?