Skip to main content
Glama

Get free practice questions

get_practice_questions
Read-onlyIdempotent

Return up to five free sample multiple-choice questions for one certification exam, each with its correct option letters and a written explanation. Use it when the user wants to practise, be quizzed or test themselves on an exam this server covers. exam is a set_id from search_exams or an official exam code such as "SAA-C03".

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>"
    },
    "name": "get_practice_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
examYes
countNo

Output Schema

NameRequiredDescriptionDefault
titleYes
exam_codeYes
questionsYes
how_to_useYes
more_questions_urlYes

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 readOnly/idempotent/closed-world, so the bar is lower; the description adds genuinely new behavior: results are capped at five, are free samples, and each includes correct option letters and a written explanation. It does not say what happens if count exceeds the cap or whether questions repeat across calls.

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?

Three sentences, front-loaded with the return payload, then the usage condition, then the key argument format. No filler and nothing repeated from the title.

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?

An output schema exists, so return values need only light treatment, and the description still summarizes them usefully. The only real gap is the `count` parameter's bounds relative to the stated five-question cap.

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 0%, so the description must carry parameter meaning. It does this well for `exam`, naming two accepted forms (a set_id from search_exams or a code like "SAA-C03"), but `count` is never mentioned except implicitly by 'up to five', leaving its range and interaction with the cap undocumented.

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 (return practice questions for one certification exam) plus the concrete payload: up to five multiple-choice questions with correct option letters and explanations. That is clearly distinguishable from siblings such as check_answer (grading) and get_exam_details (metadata).

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 an explicit triggering condition: use when the user wants to practise, be quizzed, or test themselves on a covered exam. It does not name when-not to use it or point at check_answer for grading submitted answers, so routing is clear but not complete.

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