Skip to main content
Glama

Make a quiz with Tjaz

make_quiz

Tjaz writes a multiple-choice quiz with its own AI from a description of what it's about, and the source material it's to be made from when there is any, for the people who will play it, and gives back a link to play it alone, in a 3D game or together on a big screen, and to share it. Use this when the user asks for a quiz about a subject, or from material they gave you, e.g. a chapter, their notes or a web page, and hasn't written the questions. Usually ready within a minute; if not, it gives the link where the quiz is being written, and get_quiz tells when it's ready. Tjaz writes it in the language of the description, unless language is given.

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": {
      "description": "<description>"
    },
    "name": "make_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNofun: playful; serious: plain; educational: teaches, with three facts between the questions. Default educational
publicNoWhether the user wants it on tjaz.com/quizzes, where anyone can find it. A quiz from a chat is saved for those who get its link only; the user can show it on tjaz.com/quizzes from its Share dialog on tjaz.com
playersNoWho will play the quiz. An age group: children (6–12), teens (13–17), adults (18–64), seniors (65+); or, for school, a level: grade0 is the first year of school at about 6 (kindergarten, Danish 0. klasse), grade1 to grade12 the school years after it (grade4 is US Grade 4, Danish 4. klasse, German 4. Klasse, UK Year 5; grade10–grade12 are the last three years of upper secondary school, e.g. Danish 1.g–3.g), then bachelor, master, phd, or nobel for experts. Leave it out when the user didn't say who will play: Tjaz then reads it from the description, as tjaz.com does
languageNoOptional: the language to write the quiz in, if not the description's: the language's code as Tjaz has it, ISO 639-1, e.g. da, en, ar, uk, and nb for Norwegian
materialNoOptional: the text of source material to make the quiz from, e.g. a chapter, notes or a web page the user gave you or pasted in the chat. Copy its text as it is, not a summary: Tjaz asks about what it says and makes the wrong answers from what learners often get wrong about it. Leave it out for a quiz about a subject. Tjaz keeps it in the user's source material on Tjaz, where they can make more quizzes from it or delete it
questionsNoHow many questions. Default 10
difficultyNoHow hard for those who play it. Default medium
descriptionYesWhat the quiz is about, in the user's words, e.g. "Vulkaner til 4.b, vi har læst om Island"
explanationsNoTjaz always explains after each answer why it's right or wrong, so this can be left out
material_titleNoOptional, with material: its title, e.g. "Kapitel 3: Vulkaner", which the user finds it by in their source material. Default its first line

Output Schema

NameRequiredDescriptionDefault
quizNo
statusYes
messageNoWhy it was refused, or what to tell the user

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / quiz / properties / links / properties / team
      Added value: +{
      +  "description": "Plays it on a big screen as one team against cute, silly monsters, everyone answering on their phone or laptop: the more answer right, the better the team defends, and each monster becomes its friend. Good for a class or a group of children",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / public / description
      Previous value: -"Also show it on tjaz.com/quizzes, where anyone can find it. Default false: only those who get the link can play it"New value: +"Whether the user wants it on tjaz.com/quizzes, where anyone can find it. A quiz from a chat is saved for those who get its link only; the user can show it on tjaz.com/quizzes from its Share dialog on tjaz.com"
  3. Changed1 schema field changed
    • changedOutput schema / properties / quiz / properties / links / properties / bigScreen / description
      Previous value: -"Plays it together on a big screen, everyone answering on their phone"New value: +"Plays it together on a big screen, everyone playing along on their phone or laptop"
  4. Changed2 schema fields changed
    • addedInput schema / properties / material
      Added value: +{
      +  "description": "Optional: the text of source material to make the quiz from, e.g. a chapter, notes or a web page the user gave you or pasted in the chat. Copy its text as it is, not a summary: Tjaz asks about what it says and makes the wrong answers from what learners often get wrong about it. Leave it out for a quiz about a subject. Tjaz keeps it in the user's source material on Tjaz, where they can make more quizzes from it or delete it",
      +  "maxLength": 100000,
      +  "type": "string"
      +}
    • addedInput schema / properties / material_title
      Added value: +{
      +  "description": "Optional, with material: its title, e.g. \"Kapitel 3: Vulkaner\", which the user finds it by in their source material. Default its first line",
      +  "maxLength": 200,
      +  "type": "string"
      +}
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent, closed-world write, and the description adds substantial context beyond them: usual completion within a minute, an async fallback returning a status link, language inherited from the description, and retention of supplied material in the user's source library. It also explains the link-only default visibility and the Share dialog for publishing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, but the opening sentence is a long run-on with nested clauses ('from a description of what it's about, and the source material...for the people who will play it, and gives back a link...'). The content earns its place, but the prose is wordier and less structured than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter creation tool with an output schema, the description covers the essential unknowns: when to call it, what it does with material, latency and async behavior, language default, and visibility of the resulting quiz. Nothing an agent needs to invoke it correctly is missing.

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 100%, so the schema already carries most parameter meaning and the baseline would be 3. The description still adds a rule the schema lacks: the quiz is written in the language of the description unless language is supplied, which materially affects how the language parameter should be set.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: Tjaz writes a multiple-choice quiz from a description and optional source material, returning a play/share link. It distinguishes itself from siblings by naming get_quiz as the readiness-check tool, so an agent can separate quiz creation from lookup or results.

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?

Explicitly says to use this when the user asks for a quiz about a subject or from supplied material and 'hasn't written the questions,' and points to get_quiz when the quiz is still being written. It does not address when to use save_quiz, translate_quiz or find_quizzes instead, so the routing guidance is strong but incomplete.

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