Skip to main content
Glama

Axad

Drill

show_drill
Read-only

Displays a short practice round for the learner to answer by tapping, one question at a time: choice, cloze, order or translate. It shows the progress and a score at the end. Takes 2 to 10 questions, each shaped as a quiz widget's props, and shows them as 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": {
      "title": "<title>",
      "lang": "<lang>",
      "items": "<items>"
    },
    "name": "show_drill"
  }
}

Input Schema

NameRequiredDescriptionDefault
langYesBCP 47 code of the language the questions teach: "nl".
nextNoUp to 3 one-tap next steps shown under the widget: label is the button's text, ask the message a tap sends.
itemsYesThe questions, in the order to ask them.
titleYesWhat the round practises, in a few words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already establish this is a non-destructive read-only display, so the baseline is lower. The description adds genuine behavioral context (interactive one-question-at-a-time flow, progress and score at the end, "shows them as given" meaning no reordering or randomization), but it says nothing about what happens on invalid input or how the round terminates.

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?

Three sentences, front-loaded with the core behavior and free of filler. The progress/score sentence earns its place as behavior the schema cannot express, though the final clause is slightly redundant.

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?

With four parameters, full schema coverage, and no output schema, the description is nearly sufficient: it explains interaction model, constraints, and rendering. The main residual gap is routing against the numerous show_* siblings, which matters given how many alternatives exist.

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 coverage is 100%, so the baseline of 3 applies. The description repeats the item-count constraint and the item kinds that the schema already encodes, and adds only the framing that each item is a quiz widget's props, which is marginal value beyond the structured fields.

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 ("Displays") plus the resource ("a short practice round") and enumerates the supported question kinds (choice, cloze, order, translate), so an agent can tell what it produces. It stops short of naming or contrasting any sibling such as show_quiz or show_exam_task, so the boundary is left implicit.

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?

Usage is only implied: the learner answers by tapping and the round takes 2 to 10 questions, which suggests a short interactive practice use case. There is no explicit when-to-use, when-not-to-use, or named alternative to pick instead, so the agent must infer routing.

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.