Skip to main content
Glama

Get exam details

get_exam_details
Read-onlyIdempotent

Describe one exam: the vendor's real exam (official code, question count, fee, domains and their weights) and our practice set for it (size, free questions, price, timed mock exam). exam is a set_id from search_exams or an official exam code. Use it when the user asks about an exam's format, length, fee or domains, or about our practice set for it.

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_exam_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
examYes

Output Schema

NameRequiredDescriptionDefault
domainsYes
mock_examYes
descriptionYes
practice_setYes
try_free_urlYes
official_examYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description only needs to add context — which it does by disclosing that both official exam metadata and practice-set commercial data come back in one call. No rate limits or failure modes are mentioned, but none are suggested by the annotations either.

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?

The purpose and the dual content scope are front-loaded in the first sentence, followed by parameter format, then the usage trigger. The parenthetical field lists are dense but each item maps to real returned data, so little could be cut without losing routing signal.

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 not be spelled out, and the description correctly focuses on input format and usage triggers. For a one-parameter read tool this is nearly sufficient; only explicit sibling boundaries would round it out.

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 0% and the single parameter has no description at all, so the description carries the burden — and it does, defining `exam` as either a set_id obtained from search_exams or an official exam code. That resolves the one ambiguity an agent would hit; only example formats or case-sensitivity rules are missing.

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 ("Describe one exam") and enumerates the exact payload: official code, question count, fee, domains and weights, plus practice-set size, free questions, price and timed mock. The two-sided scope (vendor exam vs. our practice set) makes it clearly distinct from question-fetching or listing siblings.

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?

"Use it when the user asks about an exam's format, length, fee or domains, or about our practice set for it" gives a concrete trigger set, and it names search_exams as the upstream source of a set_id. It stops short of explicit exclusions (e.g., use get_practice_questions for the actual items, list_exams for browsing), so an agent must still infer the boundaries.

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