Skip to main content
Glama

Read a game's prepared rounds

get_quiz
Read-onlyIdempotent

Use before editing or reusing an owned game, or to check who has joined its lobby and is ready. Returns the prepared-content revision, rounds, question count, validation issues, links, and each joined player with readiness and how many questions they submitted. Replay definitions read the frozen edition: prepared rounds include questions; private contribution rounds expose only positions and counts with contentHidden true. Never returns other players' contribution content or gameplay.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "runId": "<runId>"
    },
    "name": "get_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesThe game ID (runId) returned by create_quiz, list_quizzes or get_quiz.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, closed read, and the description goes further: it discloses the privacy boundary ('never returns other players' contribution content or gameplay'), the redaction behavior ('contentHidden true', positions and counts only), and the frozen-edition semantics for replays. It also scopes the tool to owned games.

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, front-loaded with the usage trigger, then returns, then the privacy/frozen-edition rules. No filler, and the most decision-relevant constraint (ownership plus privacy) is not buried.

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?

An output schema exists, yet the description still supplies the non-obvious semantics an agent cannot get from schema alone: content redaction for private contribution rounds, frozen-edition replay reads, and ownership scoping. Nothing needed to call this 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?

Only one parameter and schema coverage is 100%, with the schema already explaining that runId is the game ID from create_quiz, list_quizzes or get_quiz. The description adds little beyond implying the game must be owned; 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?

States a specific verb and resource ('Read a game's prepared rounds') and immediately grounds it in the authoring workflow. It also distinguishes itself behaviorally from get_authoring_context and replay_game by noting that replay definitions read the frozen edition while this returns prepared content with validation issues and lobby readiness.

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?

Gives two concrete triggers: 'before editing or reusing an owned game' and 'to check who has joined its lobby and is ready.' It does not name a sibling as the alternative or state when not to use it, but the usage context is unambiguous.

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