Skip to main content
Glama

Search certification exams

search_exams
Read-onlyIdempotent

Find certification exams by official code (e.g. "SAA-C03", "CIPP/E"), name (e.g. "Azure Administrator") or topic (e.g. "GDPR"). Returns the matching practice sets with their size, free questions and price. Use it when the user names an exam or certification, to see whether it is covered and get its set_id.

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": {
      "query": "<query>"
    },
    "name": "search_exams"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes
catalog_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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine value by disclosing the return payload (practice sets with size, free questions, price) and the set_id hand-off. It omits match behavior (fuzzy vs exact) and what an empty result means.

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, each load-bearing: the first defines inputs with examples, the second defines the return shape, the third defines the trigger and the set_id outcome. Nothing is repeated from the schema or annotations.

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?

With an output schema present, the description is not obligated to explain return values, yet it usefully summarizes them. A 2-parameter tool is well covered overall; the only material gap is the `limit` semantics and result-set behavior on no matches.

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 0%, so the description must compensate. It does well for `query`, spelling out that codes, names and topics are all accepted with examples. It says nothing about `limit` (default 5, caps result count), leaving half the parameters 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+resource ("Find certification exams") and enumerates the three query modes with concrete examples ("SAA-C03", "Azure Administrator", "GDPR"). An agent can immediately distinguish this targeted lookup from the broader list_exams sibling.

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?

Explicitly scopes usage: "Use it when the user names an exam or certification, to see whether it is covered and get its set_id." That gives a clear trigger plus the downstream purpose (fetching set_id). It stops short of naming alternatives (e.g. list_exams for browsing) or stating when not to use it.

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