Riddle

stats_user_breakdown

Read-onlyIdempotent

Returns an account-wide stats summary for the authenticated user: one row per Riddle with its views, starts, submissions and active time, plus the totals across every Riddle in scope. Ranked by sortBy and returned 25 Riddles per page ("hasMore" says whether another page exists). This is intentionally a summary, not a deep breakdown - for a Riddle's blocks, choices and form fields call stats_riddle_breakdown with its ID, and for one project's full breakdown call stats_project_breakdown. On accounts with many projects, narrow the scope with projectIds. Requires a user API key — will fail with project API keys.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number, 1-indexed (default: 1). Zero or negative is rejected with a VALIDATION_ERROR, not clamped to page 1 - the same contract as riddle_list/project_list.
`dateTo`	No	End date (inclusive), format: YYYY-MM-DD, e.g. "2026-01-31". Optional, defaults to today.
`sortBy`	No	Metric the Riddles are ranked by before the page is cut: "views" (default), "starts", "submissions" or "timeActive". Sorting always spans the whole account (or the projects given), so page 1 is genuinely the top of the account.
`dateFrom`	No	Start date (inclusive), format: YYYY-MM-DD, e.g. "2026-01-01". Optional, defaults to 30 days ago.
`projectIds`	No	Narrow the summary to these project IDs (array of integers, from project_list). Omit to cover the whole account, including the personal project. Passing a project the user cannot view stats of is an error, not a silently skipped project.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses pagination behavior (25 per page, hasMore), account-wide ranking semantics, the summary/deep-breakdown distinction, and the user API key requirement. This adds meaningful behavioral context that structured 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 three sentences long, front-loaded with the main purpose, followed by pagination and then by sibling routing with scope and auth guidance. Every sentence earns its place; there is no filler or repetition of schema fields.

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 no-output-schema tool with multiple related siblings, the description covers the necessary scope, return summary, pagination mechanics, hasMore, auth requirements, and alternative paths. It is complete enough for an AI agent to know when and how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% coverage, thoroughly documenting all parameters and their defaults. The description adds extra context for projectIds, such as narrowing scope on accounts with many projects, and confirms sortBy semantics. Most parameter meaning is already in the schema, so baseline 3 is appropriate.

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 first sentence states a specific resource and action: account-wide stats summary for the authenticated user, one row per Riddle with views, starts, submissions, and active time, plus totals. It also explicitly names stats_riddle_breakdown and stats_project_breakdown as distinct alternatives, so an agent can differentiate this tool from its siblings.

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 says when to use this tool versus alternatives: for a summary use this, for a Riddle-level breakdown call stats_riddle_breakdown, for one project's full breakdown call stats_project_breakdown. It also gives practical usage context for narrowing many projects with projectIds and warns about authentication requirements.

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?