Skip to main content
Glama

List quizzes

list_authorized_quizzes
Read-onlyIdempotent

List the quizzes this connection can read in its authorized library. With Full library access this includes every quiz there. Every item includes its editorUrl for the user. Pass nextCursor as after to continue.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_authorized_quizzes"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
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.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds two useful behaviors beyond that: results carry an editorUrl, and pagination continues by feeding nextCursor into 'after'. It still says nothing about result ordering or what an empty authorized library returns.

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?

Three short sentences, front-loaded with the scope, then result contents, then pagination. No redundant restatement of the name or title; each sentence carries distinct information.

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 no output schema, the description usefully notes editorUrl per item and the cursor field for continuation, which is most of what an agent needs. Minor gaps remain around the absence of results and ordering, but nothing blocking.

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 only 50% – 'after' has no schema description – and the description compensates by explaining that after is the nextCursor continuation token. The library enum is already documented in the schema, so the description adds value mainly where the schema is silent.

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 ('List the quizzes') plus an explicit scope ('this connection can read in its authorized library'), which separates it from read_quiz and the version-listing sibling. It stops short of naming an alternative, but the scope statement is precise enough to route correctly.

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?

It clarifies access scope ('With Full library access this includes every quiz there') and tells the agent how to paginate, which is genuine usage guidance. However, it never says when to prefer this over read_quiz or list_quiz_versions, and the personal-vs-organization choice is only explained in the schema, not the description.

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