Skip to main content
Glama

Create a vocabulary quiz

practice_quiz
Read-only

Create a short HSK vocabulary quiz (1-10 multiple-choice questions) for a level: meaning, pinyin, fill-in-the-blank, or mixed. Answers are not included; show the questions to the user, collect their choices, then call grade_answers with the quiz_id.

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": {
      "level": "<level>"
    },
    "name": "practice_quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoQuestion type (default mixed); cloze is fill-in-the-blank
countNoNumber of questions, 1-10 (default 5)
levelYesHSK 3.0 level: 1-6, or "7-9" for the advanced band
topicNoOptional topic tag, e.g. food or travel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, non-destructive, closed-world, and non-idempotent, so the safety profile is covered. The description adds genuinely new behavioral information beyond that: answers are intentionally withheld from the result, the questions must be surfaced to the user, and a quiz_id is returned for the follow-up grade_answers call. Minor gap: it does not say how long a quiz_id remains valid or how the quiz is stored.

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 sentences, front-loaded with the core action and constraints, then the follow-up workflow. No filler or repetition; every clause carries either a scope limit or a next-step instruction.

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?

For a generation tool with no output schema, the description conveys enough: it implies the response contains questions plus a quiz_id, and explicitly notes the absence of answers. Slightly more detail on the returned structure would remove the remaining inference, but nothing essential is missing.

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%, so level, count, type, and topic are already fully documented with enums and defaults. The description reinforces the question-type set and the 1-10 range and clarifies that questions are multiple-choice, but adds little beyond what the schema already states.

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?

The description opens with a specific verb and resource ("Create a short HSK vocabulary quiz") and bounds it with a question count (1-10) and question types (meaning, pinyin, fill-in-the-blank, mixed). It also distinguishes this creation step from the sibling grade_answers, which handles the subsequent grading step.

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?

It clearly prescribes the workflow: create the quiz, show the questions to the user, collect their choices, then call grade_answers with the quiz_id. It does not state explicit when-not-to-use conditions or contrast with the other HSK lookup/list siblings, but the usage context is unambiguous.

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