Skip to main content
Glama

Edit a game's prepared rounds

update_quiz
DestructiveIdempotent

Use for follow-up edits after get_quiz. Updates the game at expectedRevision while it is still an editable lobby. Keep stable question/round IDs. Accepts title, blocks and partial settings; omitted fields are preserved. Set contributions to optional with questionsPerContributor for a requested per-person maximum, or disabled to close submissions while retaining existing content. 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>",
      "runId": "<runId>",
      "expectedRevision": "<expectedRevision>",
      "content": "<content>"
    },
    "name": "update_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesThe game ID (runId) returned by create_quiz, list_quizzes or get_quiz.
contentYes
requestIdYesStable UUID for this intent. Reuse it with identical arguments after a lost response; use a new UUID for a different action.
expectedRevisionYesUse the prepared-content revision returned by 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 destructiveHint=true and idempotentHint=true, yet the description still adds real behavior: partial update with omitted fields preserved, the requirement to keep stable question/round IDs, and requestId reuse for identical retries after a lost response. These details materially change how an agent constructs a safe retry and avoids churning IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use case and precondition, then constraint, then setting semantics, then retry rule — no filler sentences. It is dense to the point of being telegraphic in places ('Accepts title, blocks and partial settings'), but nothing is wasted.

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 and annotations cover the safety profile, so the description focuses correctly on preconditions and edit semantics. The remaining gap is revision-conflict behavior — what happens if expectedRevision is stale — which matters for a tool whose whole guardrail is that field.

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

Parameters4/5

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

Schema coverage is 75%, so the schema carries most parameter documentation, but the description adds genuine semantics the schema cannot express: expectedRevision is the value from get_quiz, and contributions=optional is coupled with questionsPerContributor as a per-person maximum while disabled closes submissions without discarding content. Minor gap: it does not state whether omitting a block from the blocks array deletes it.

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 (updates the game's prepared rounds), ties it to a lifecycle stage ('editable lobby'), and anchors it to get_quiz for the revision. An agent can distinguish it from create_quiz or cancel_lobby without opening the schema.

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 explicit when-to-use ('follow-up edits after get_quiz') and an implicit when-not ('while it is still an editable lobby'), plus conditional guidance for the contributions setting. It stops short of naming create_quiz as the alternative for new games or saying what to do once the lobby is no longer editable.

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