Skip to main content
Glama

AIML Rounds

Topic quiz

quiz
Read-only

Multiple-choice questions for a roadmap topic (e.g. 'Linear algebra', 'RAG', 'Inference and serving'). Answers stay hidden unless reveal_answers is true: ask the learner first, then call again with reveal_answers to grade and explain. No topic: list topics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "quiz"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many questions (default: all)
topicNoTopic id or name
reveal_answersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the hidden-by-default answers and the ask-then-reveal two-call pattern. It says nothing about response shape or how many questions are returned by default, leaving some behavioral gaps.

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 tight clauses, front-loaded with what the tool returns before covering the reveal workflow and the no-topic case. Little waste, though the phrasing is compressed into a run-on line rather than organized steps.

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 simple read-only tool with zero required params and no output schema, the description covers purpose, the two-call grading workflow, and the no-topic path. Minor gaps: default question count and whether grading feedback text accompanies revealed answers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds real meaning beyond the 67%-covered schema: reveal_answers controls whether answers/grading explanations are exposed, and topic accepts a name or id with a documented no-topic fallback. The count parameter's semantics (beyond its schema default/min/max) are not discussed, but the key mode-switching parameter is well explained.

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?

States a specific resource (multiple-choice questions) scoped to a roadmap topic, with concrete topic examples and a defined no-topic fallback (list topics). An agent can distinguish this from roadmap/get_lesson siblings, though the verb is implicit rather than named.

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 explicit two-step workflow guidance: answers stay hidden unless reveal_answers is true, ask the learner first, then call again to grade. Also defines the no-topic behavior. It lacks any explicit routing against sibling tools (e.g., get_lesson vs quiz), so it is clear context without named alternatives.

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