whyismy-org

Find WhyIsMy.org quizzes

list_quizzes

Read-onlyIdempotent

Find WhyIsMy.org's free ten-question quizzes (health, tech, cars, home and eldercare topics) with instant explanations and a certificate of completion. Both arguments are optional: omit everything to browse, pass query and/or category to narrow. Each result is a one-line teaser plus a link — a quiz is interactive and scores the user in their own browser, so send the user to the URL to take it instead of answering the questions yourself.

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": "list_quizzes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results, 1-25. Default 5.
`query`	No	What the user wants to be quizzed on, e.g. "itchy skin" or "medicaid look-back".
`category`	No	Optional category name to filter, e.g. "Skin", "Dental", "Finance".

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already establish read-only/idempotent/non-destructive, and the description adds real behavioral context: results are one-line teasers plus a link, and the quiz is interactive/scored in-browser so the agent must not answer questions itself. That is exactly the kind of non-obvious behavior an agent needs.

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?

Three sentences, each with a distinct job: what the tool is, how to invoke the optional filters, and how to handle results. Front-loaded with the resource and zero filler.

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 no output schema, the description still conveys the return shape (teaser line + link) and the crucial interaction rule for using results. For a simple optional-filter list tool, nothing needed to call it correctly is missing.

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?

Schema coverage is 100% with per-parameter descriptions, so the baseline is 3. The description adds combination semantics ('pass query and/or category'), though it says 'both arguments' when three exist, so it neither compensates for nor meaningfully exceeds 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?

States a specific verb+resource ('Find ... quizzes'), names the domain topics, and adds distinguishing detail (ten-question, instant explanations, certificate) that separates it from sibling article/calculator tools.

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?

Explicitly says both arguments are optional and how to browse vs narrow ('omit everything to browse, pass query and/or category to narrow'), plus a clear when-to-use directive to send the user to the URL. It does not name sibling tools as alternatives, which keeps it just short of a 5.

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

All whyismy-org 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?