Skip to main content
Glama

AI Certificates

by study.aicertificates
OverviewDiscussionsAdmin

Get a practice question

get_practice_question
Read-only

Returns one original practice question with its options and no answer key. Present it to the user and let them choose before calling check_answer. Pass every id already served in exclude_ids — this server is stateless and remembers nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
examYesExam slug from list_exams.
focusNoOptional ordering by how everyone else answers these questions: "hardest" serves the highest crowd miss rates first, "traps" serves the questions most people get wrong the SAME way — a shared misconception rather than merely a hard question. Nothing is filtered out; questions with no crowd data simply come last.
domainNoOptional domain id (e.g. "d3") to drill one area. Domain ids come from list_exams.
exclude_idsNoQuestion ids already served in this session, so they are not repeated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / focus
      Added value: +{
+  "description": "Optional ordering by how everyone else answers these questions: \"hardest\" serves the highest crowd miss rates first, \"traps\" serves the questions most people get wrong the SAME way — a shared misconception rather than merely a hard question. Nothing is filtered out; questions with no crowd data simply come last.",
+  "enum": [
+    "hardest",
+    "traps"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true, and the description adds meaningful behavioral context beyond that: it returns no answer keyable, and 'this server is stateless and remembers nothing,' which explains why exclude_ids is essential. This is valuable information an agent needs before calling the tool successfully.

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?

The entire description is two sentences with no filler. It front-loads the core result, then immediately gives the next step and the statelessness caveat. Every word earns its place.

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 four well-documented parametersched, the description covers what the tool returns, what it intentionally omits, and how to feed it state. It could mention the shape of the returned question id explicitly, but the stateless exclude_ids instruction is sufficient context for an agent to use it correctly.

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?

Schema coverage is 100%, so the schema already documents all four parameters. The description adds important semantic context for exclude_ids by stressing 'every id already served' and explaining the statelessness that makes it necessary. It does not add much for exam, focus, or domain, but the schema already covers those thoroughly.

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 states a specific action and resource: 'Returns one original practice question with its options and no answer key.' It also distinguishes itself from sibling tools by explicitly positioning it before 'check_answer' and clarifying it does not reveal answers, which separates it from answer-checking and progress tools.

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?

The description gives clear workflow guidance: 'Present it to the user and let them choose before calling check_answer.' It also instructs the caller to pass all served ids via exclude_ids due to statelessness. It does not explicitly name alternatives or when not to use this tool, but the sequencing guidance is strong enough for correct invocation.

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

All AI Certificates toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources