Skip to main content
Glama

Restore quiz version

restore_quiz_version
DestructiveIdempotent

Pro only: restore a revision from list_quiz_versions as the quiz's new current revision. Pass the current revision as baseRevision. A shared quiz returns a review link for the host. On any plan, earlier content still in this chat can be reapplied with edit_quiz.

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": {
      "quizId": "<quizId>",
      "revision": "<revision>",
      "baseRevision": "<baseRevision>",
      "operationId": "<operationId>"
    },
    "name": "restore_quiz_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
quizIdYes
libraryNoUse personal for My quizzes, or organization when the user asks for their organization library. Omitting the library selects personal.
revisionYes
operationIdYesGenerate one UUID per restore; reuse it exactly on a retry.
baseRevisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the plan gate, the optimistic-concurrency requirement (baseRevision must be the current revision), and an output behavior for shared quizzes (a review link for the host). It stops short of stating that the previously current revision is replaced and whether that content remains recoverable via version history, which matters for a destructiveHint=true operation.

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?

Four short sentences, front-loaded with the gating constraint, then the concurrency rule, then the return behavior, then the fallback. Nothing is repeated from the title and no sentence is filler.

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?

For a destructive 5-parameter mutation with no output schema, it covers plan gating, the concurrency token, and the shared-quiz return value, which is most of what an agent needs. It omits what happens when baseRevision is stale (conflict vs. overwrite) and what is returned for a non-shared quiz.

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?

With only 40% schema coverage, the description carries real weight and does explain baseRevision as the current revision used as the concurrency token, which is the least guessable parameter. It leaves revision itself underspecified (which revision to pass, and whether it must come from list_quiz_versions) while library and operationId are already documented in 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?

States a specific verb (restore) and resource (a revision, made the quiz's new current revision), and names the sibling that supplies the input (list_quiz_versions). It also draws the line against edit_quiz, so an agent can pick 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 precondition (Pro plan only), tells the agent where revisions come from (list_quiz_versions), and names the alternative path for non-Pro users (reapply earlier chat content with edit_quiz). When-to-use and when-to-use-something-else are both covered.

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