Skip to main content
Glama

list_quizzes

Read-onlyIdempotent

List the quizzes the signed-in user has on quizquiz.co, newest first, with preview and edit links. Use this to answer questions about what quizzes someone already has.

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

NameRequiredDescriptionDefault
limitNoHow many quizzes to return, newest first. Defaults to 20, maximum 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld. The description adds useful context beyond that: results are user-scoped, ordered newest first, and include preview and edit links. It does not discuss limits/pagination behavior beyond the schema or empty-result behavior, but it meaningfully supplements the annotations.

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?

Two tight sentences with the resource and scope front-loaded followed by the usage cue. Every clause earns its place; no 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?

For a one-parameter read tool with no output schema and rich annotations, the description covers what the tool returns (preview and edit links), ordering, and user scoping. An agent has everything needed to call 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?

Schema coverage is 100% and the single limit parameter is fully documented with default and maximum. The description only echoes the "newest first" ordering already in the schema, so baseline 3 applies.

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 (list) and resource (quizzes on quizquiz.co) plus scope (signed-in user's own quizzes), ordering (newest first), and returned content (preview and edit links). This is unambiguous and clearly distinct from the sibling create_quiz.

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?

"Use this to answer questions about what quizzes someone already has" gives a clear triggering context. It stops short of naming exclusions or pointing at create_quiz as the alternative for write operations, so it lacks the explicit when-not guidance of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources