Skip to main content
Glama

List quiz versions

list_quiz_versions
Read-onlyIdempotent

Pro only: list an authorized quiz's saved revisions, newest first, with when each was saved. Pass nextBeforeRevision as beforeRevision to continue. Give the user the editorUrl to see them in Rondilo. 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>"
    },
    "name": "list_quiz_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
quizIdYes
libraryNoUse personal for My quizzes, or organization when the user asks for their organization library. Omitting the library selects personal.
beforeRevisionNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the description is credited for what it adds: plan gating, newest-first ordering, and a pagination cursor contract ("Pass nextBeforeRevision as beforeRevision to continue"). It also directs the agent to surface editorUrl to the user, which matters because no output schema exists. What remains undisclosed is the failure mode for a non-authorized quiz.

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 plan constraint, then purpose, then the cursor mechanic, then the alternative. 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?

For a three-parameter read tool with no output schema, the description covers ordering, pagination, plan gating, the user-facing editorUrl, and the closest alternative. It falls short only on authorization failure behavior, which is a minor gap given the richness already provided.

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 only 33% – library is documented, quizId and beforeRevision are not. The description does compensate for beforeRevision by explaining it as the continuation cursor using the returned nextBeforeRevision, but quizId's accepted form and the library interaction with it are left entirely implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ("list an authorized quiz's saved revisions") plus the ordering and the time information returned, so an agent knows exactly what comes back. It never names restore_quiz_version or read_quiz as the divergent siblings, so differentiation is by scope (revisions list) rather than explicit routing.

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?

It gives a hard precondition ("Pro only") and an explicit alternative path: on any plan, earlier in-chat content is reapplied with edit_quiz rather than through this tool. That is real when-to-use/when-not-to-use guidance, though it does not tell the agent what to do if the plan check fails.

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