Skip to main content
Glama

Set up a rematch

replay_game
Idempotent

Use when the user wants to play a finished game again with exactly the same questions. Pass replayEditionId from list_quizzes. Creates a new lobby with a fresh invitation; a rematch cannot be edited (use create_quiz with the old rounds for an edited version). Never starts play. Reuse requestId for identical retries.

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": {
      "requestId": "<requestId>",
      "editionId": "<editionId>"
    },
    "name": "replay_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicknameNoHost player name. Use Host when no name was supplied.Host
editionIdYesreplayEditionId from list_quizzes.
requestIdYesStable UUID for this intent. Reuse it with identical arguments after a lost response; use a new UUID for a different action.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description explains that a new lobby and fresh invitation are created, that the rematch cannot be edited, and that play never starts. It also explains retry semantics for requestId, which is meaningful behavioral context.

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 front-loaded with the usage trigger, then moves through source parameter, side effect, exclusion, and retry rule. Every sentence carries useful information with 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?

Annotations cover safety and idempotency, the schema fully documents parameters, and an output schema exists. The description adds the operational details an agent needs: what is created, what is not started, and when to use an alternative tool.

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%, so the schema already documents all parameters including editionId and requestId. The description repeats that replayEditionId comes from list_quizzes and that requestId should be reused for identical retries, but adds no syntax or meaning beyond 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?

The description states a specific verb and resource: replaying a finished game with exactly the same questions, producing a new lobby. It explicitly distinguishes this from create_quiz when an edited rematch is desired.

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?

It gives clear when-to-use guidance: when the user wants the same questions again. It names list_quizzes as the source of replayEditionId and explicitly routes edited rematches to create_quiz, leaving little ambiguity.

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