Skip to main content
Glama

generate-quiz

Generates PMP-style multiple-choice questions from a course chapter in PMI exam format, including situational questions, four options, and explanations. Requires an index built first.

Instructions

Generates PMP-style multiple choice questions (MCQ) from a chapter of your course. Questions follow the PMI exam format: situational, 4 options, one best answer with explanation. Requires the index to be built first with extract-document-index.

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": {
      "chapter": "<chapter>"
    },
    "name": "generate-quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of questions to generate (default: 5)
domainNoPMI domain focus (default: all)
chapterYesChapter number to generate questions from
documentNoDocument name (use list-documents to see available). Auto-detected if only one document is indexed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It usefully discloses the generated output format (PMI exam style, one best answer with explanation) and the indexing dependency, but says nothing about latency, cost per question, whether results are persisted, or error behavior for an unindexed document or out-of-range chapter.

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 tightly written sentences with the core purpose front-loaded and the prerequisite second. No filler, though the format clause could be compressed slightly.

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 four-parameter generation tool with no annotations and no output schema, the description supplies the essential facts: source granularity, output format, and the required index prerequisite. Only failure modes and generation cost are absent, which are secondary for correct invocation.

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 all four parameters (count, domain, chapter, document) are already documented with defaults and enum values. The description adds only that questions come from a single chapter and follow PMI format; it adds no syntax or constraint detail beyond the schema, so baseline 3 applies.

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 ('Generates PMP-style multiple choice questions (MCQ)') and narrows the source ('from a chapter of your course'). The output shape (situational, 4 options, one best answer with explanation) further distinguishes it from generic document Q&A siblings like ask-document.

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?

Gives a concrete precondition: 'Requires the index to be built first with extract-document-index', which tells the agent the correct ordering of tool calls. It stops short of explicit when-not guidance (e.g., what to do if no index exists or the chapter is out of range), so it is clear context but not full routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.