Skip to main content
Glama

create_quiz

Create a new quiz on quizquiz.co with the provided questions. Returns a shareable link to the 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": {
      "name": "<name>",
      "rounds": "<rounds>"
    },
    "name": "create_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name/title of the quiz
roundsYesArray of rounds, each containing questions
descriptionNoOptional description of the quiz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, openWorld=true, idempotent=false), so the safety bar is lower. The description adds one genuinely useful piece of behavior — that a shareable link is returned — but says nothing about authentication, validation failures, or whether repeated calls create duplicate quizzes (relevant given idempotent=false).

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?

Two short sentences, action first and return value second, with no filler. Every sentence earns its place.

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?

No output schema exists, but the description covers the return value (shareable link) and the schema fully documents the nested payload, so an agent can call it correctly. Minor gaps remain around auth and quiz visibility that would have made it complete.

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 description coverage is 100%, including the nested rounds/questions shape and the 'exactly 4 options' constraint, so the baseline is 3. The description only says "with the provided questions" and adds no semantics beyond what the schema already documents.

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 ("Create a new quiz") plus the target platform and the return value (a shareable link). It doesn't explicitly name the sibling list_quizzes or contrast with it, but the create-vs-list distinction is obvious from the name and wording.

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

Usage Guidelines2/5

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

The description gives no guidance on when to reach for this tool versus list_quizzes, and no prerequisites are mentioned (account/auth, whether published quizzes are public or editable). Usage is only inferable from the verb.

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