Skip to main content
Glama

Find my games

list_quizzes
Read-onlyIdempotent

Use when the user wants to find, edit, reuse or replay a game they hosted earlier. Returns their own games newest first, with player counts and replayEditionId when a finished game can be played again exactly; get_quiz retrieves the full content.

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
queryNo

Output Schema

NameRequiredDescriptionDefault

No arguments

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, closed-world behavior, and the description still adds real substance: results are restricted to the user's own games, ordered newest first, and replayEditionId is populated conditionally when a finished game can be replayed exactly. It does not mention pagination, result limits, or whether the optional query narrows across name/description, which is the remaining behavioral gap.

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 compact sentences, both front-loaded with the trigger first and the return shape plus sibling routing second. No filler or restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the return shape needn't be explained, and annotations cover the safety profile; together with the description's ordering and conditional-field notes an agent has enough to call it correctly. The one missing piece is any explanation of the optional `query` parameter.

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

Parameters2/5

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

The single optional `query` parameter has 0% schema description coverage and is never mentioned in the description, so nothing indicates what it matches against (title, opponent, date?) or how its 120-character limit relates to behavior. For a one-parameter tool the description should carry this burden and does not.

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 and scope: it returns the caller's own games, newest first, with player counts and replayEditionId. It also explicitly distinguishes itself from get_quiz, which 'retrieves the full content,' so an agent can route between the two without opening either schema.

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?

Gives an explicit trigger ('when the user wants to find, edit, reuse or replay a game they hosted earlier') and names the alternative for the detail-fetching case. The only mild looseness is including 'edit' as a trigger for a read-only listing tool, but the intended workflow is clear.

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