Skip to main content
Glama

Read quiz

read_quiz
Read-onlyIdempotent

Read an authorized quiz, including authored slides, correct answers, revision and editorUrl. Give the user this link when they want to open the quiz in Rondilo.

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": "read_quiz"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context on top: it discloses that the response exposes correct answers (sensitive content the agent may need to handle carefully) and the editorUrl, and scopes the read to "authorized" quizzes. It does not say what happens on an unauthorized or missing quizId, which is the only notable gap.

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?

Two sentences, front-loaded with the operation and its payload, followed by the one user-facing action the tool enables. No filler. Minor weakness: "this link" appears before editorUrl is explicitly connected to it, requiring a small inference.

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?

With annotations covering safety and no output schema, the description is responsible for telling the agent what comes back, and it does so by naming the key returned fields. For a simple read-only tool with only one required parameter, this is largely sufficient. The unexplained quizId and the unaddressed failure mode for unauthorized access keep it from being complete.

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

Parameters2/5

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

Schema coverage is 50%: the library parameter is fully documented in the schema including its default, but quizId carries only type and length constraints with no description. The description does not compensate — it never explains what quizId is, what format it takes, or how to obtain one, and does not mention the library parameter at all. The single word "authorized" is the only added semantic framing.

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?

States a specific verb and resource ("Read an authorized quiz") and enumerates what the payload contains: authored slides, correct answers, revision and editorUrl. That is well beyond a restatement of the name. It stops short of explicitly contrasting with siblings such as list_authorized_quizzes or edit_quiz, so sibling differentiation is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence gives a conditional usage cue — surface the editorUrl when the user wants to open the quiz in Rondilo — which is genuine when-to-use guidance for the returned link. However, there is no guidance on when to call this versus listing or editing a quiz, and no mention of the authorization precondition beyond the adjective "authorized".

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