Skip to main content
Glama

Create quiz

create_quiz
Idempotent

Save the complete presentation or quiz as one new quiz in the connected library and return its editorUrl. Give this link to the user so they can open the quiz themselves. Combine info slides with quiz questions in the requested order. Leave out theme so an organization quiz starts on its organization's default colors. When the user asks for another look, set theme to "party" or to {kind:"business",main:"#1d4ed8",second:"#0d9488"}.

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": {
      "operationId": "<operationId>",
      "quiz": "<quiz>"
    },
    "name": "create_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
quizYes
libraryNoUse personal for My quizzes, or organization when the user asks for their organization library. Omitting the library selects personal.
operationIdYesOne UUID for this creation, for example 17af9929-f381-4a25-b0e3-32e9d036fa28. Generate a new UUID for each quiz and keep it on retries.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, and the description reinforces idempotency by tying operationId to retries ("keep it on retries"). It adds behavior beyond the annotations by disclosing the returned editorUrl and who should receive it, plus the default-theme side effect for organization quizzes. It does not say what happens on a duplicate or conflicting operationId beyond reuse.

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?

Four sentences, front-loaded with the core action and return value, followed by usage and theming guidance. The inline example theme object is verbose but earns its place as a literal value the agent must reproduce. Minor redundancy between the first and second sentences about the editor link.

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 complex nested-schema creation tool with no output schema, the description states the return value (editorUrl) and ordering semantics ("combine info slides with quiz questions in the requested order"). Slide-construction detail is correctly delegated to the rich schema. The only real gap is the undocumented placement of the theme field it references.

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 67% schema coverage the schema already documents library and operationId well. The description's main added value concerns theme, a field that does not appear in the top-level schema properties, so it adds meaning but leaves the agent guessing where theme belongs. It also adds nothing about the required quiz payload beyond what the schema already spells out.

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 opens with a specific verb and resource: "Save the complete presentation or quiz as one new quiz in the connected library and return its editorUrl." That is concrete enough for an agent to know this creates a new quiz rather than modifying one. It does not, however, differentiate itself from siblings like edit_quiz or attach_quiz_media.

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 gives useful post-call guidance ("Give this link to the user so they can open the quiz themselves") and conditional theming rules (omit theme for a default-colored org quiz, use "party" or a business object when the user asks for another look). What it never states is when to call this instead of edit_quiz, or any prerequisite such as an existing connection or authorization.

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