Skip to main content
Glama

Axad

Exam task

show_exam_task
Read-only

Displays one practice item in an exam's own format, for a learner who wants exam practice: a short text, a question, options and an optional timer. The view checks the pick and shows the 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": {
      "exam": "<exam>",
      "text": "<text>",
      "ask": "<ask>",
      "options": "<options>",
      "answer": "<answer>",
      "explain": "<explain>",
      "lang": "<lang>"
    },
    "name": "show_exam_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
askYes
examYes
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.
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.
textYes
glossNo
answerYes
explainYes
optionsYes
secondsNo

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.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint/non-destructive, and the description adds real behavioral context beyond them: the view is interactive, it 'checks the pick and shows the explanation', and the timer is optional. It still does not say what happens on an incorrect pick or whether state is retained, which is why it stops short of 5.

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?

Two sentences, front-loaded with the verb and the rendered content, with no filler. The colon-separated list is dense but readable; it could be tighter only marginally.

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?

With 11 parameters, 7 of them required, no output schema, and low schema coverage, this is an underspecified definition. An agent must guess at `answer`, `exam`, `gloss` and the interaction rules for a fairly complex widget, which is well beyond what two sentences support.

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?

Schema description coverage is only 27%, so the description must carry the load, and it covers only text, ask, options, seconds and explain by implication. The required `answer` parameter is a bare number with no stated meaning (correct-option index?), and `exam` and `gloss` are never mentioned at all.

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 gives a specific verb and resource — 'Displays one practice item in an exam's own format' — and enumerates the content (short text, question, options, optional timer). It is clear what the tool produces, though it never differentiates itself from close siblings like show_quiz or show_drill.

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?

'for a learner who wants exam practice' supplies a usage context, so an agent can infer the scenario. However, there is no explicit when-not guidance and no named alternative for the adjacent quiz/drill cases, leaving selection 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.