Skip to main content
Glama

Axad

Quiz

show_quiz
Read-only

Displays one quick question for the learner to use what was just shown: choice, cloze, order or translate. The view checks the answer and shows the result with an explanation.

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": {
      "kind": "<kind>",
      "ask": "<ask>",
      "answer": "<answer>",
      "explain": "<explain>",
      "lang": "<lang>"
    },
    "name": "show_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
askYes
foldNotrue: a secondary widget of this reply, made now and shown folded: only its title row, until one click opens it. Omit it on the reply's main widgets, which show open.
kindYes
langYesBCP 47 code of the language the widget teaches: "nl". The view speaks and saves its words in it.
nextNoUp to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.
glossNo
answerYes
promptNo
explainYes
optionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Up to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.",
      +  "items": {
      +    "properties": {
      +      "ask": {
      +        "description": "The message a tap sends, in the learner's words.",
      +        "maxLength": 300,
      +        "type": "string"
      +      },
      +      "label": {
      +        "description": "The button's text.",
      +        "maxLength": 32,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "label",
      +      "ask"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 3,
      +  "type": "array"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds real behavioral value by saying the view checks the answer and returns a result with an explanation, but it does not explain the non-idempotent nature (each call presumably renders a new widget) or what the learner sees on an incorrect answer.

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 tight sentences with no filler, front-loading what is displayed and then how it behaves. Every clause carries information the agent can use.

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

Completeness2/5

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

For a tool with 10 parameters, 5 required, no output schema, and low schema coverage, the description is too thin. It never explains how answer format depends on kind (choice vs. cloze vs. order vs. translate) or what prompt, gloss, options, next, and fold are meant to carry, leaving the agent to reverse-engineer the payload from terse schema fragments.

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?

With 10 parameters and only 30% schema description coverage, the description needs to compensate and does not: ask, answer, explain, gloss, prompt, options, and kind-shape relationships are never mentioned. Only the kind values are implicitly echoed, and those are already in the enum, so the description adds almost no meaning beyond the schema.

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?

Uses a specific verb ("Displays") with a concrete resource ("one quick question") and enumerates the four question kinds (choice, cloze, order, translate), which matches the kind enum. It stops short of differentiating itself from close siblings such as show_drill or show_exam_task, so an agent must infer the boundary.

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 phrase "for the learner to use what was just shown" implies the usage context: a short check immediately after instruction. There is no explicit when-not guidance and no named alternative (e.g., drill vs. exam task), so routing between siblings is left to inference.

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.