Skip to main content
Glama

List exams by vendor

list_exams
Read-onlyIdempotent

Without a vendor, list the certification vendors covered and how many exams each has. With a vendor (a name such as "Microsoft Azure" or a code such as "aws", "iapp", "isc2"), list that vendor's exams. Use it when the user asks which vendors or exams are covered.

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": "list_exams"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorNo

Output Schema

NameRequiredDescriptionDefault
examsNo
vendorNo
vendorsNo
catalog_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: the output shape changes depending on whether vendor is supplied, which is not derivable from annotations or schema.

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 carrying distinct information (no-vendor behavior, with-vendor behavior and accepted formats, usage trigger), with the most important distinction front-loaded.

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-value detail is unnecessary, and both invocation modes are covered. Remaining minor gaps: no statement on partial/case-insensitive vendor matching or what happens for an unknown vendor string.

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 parameter is undocumented in the schema, so the description must compensate. It does so well: vendor accepts either a name like "Microsoft Azure" or a code like "aws", "iapp", "isc2", and the null/omitted behavior is spelled out.

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?

Names a specific verb and resource and clearly delineates two modes: vendor omitted returns vendors plus per-vendor exam counts, vendor supplied returns that vendor's exams. It does not distinguish itself from the sibling search_exams, which an agent must infer.

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 states the trigger condition ("Use it when the user asks which vendors or exams are covered"), which covers both branches of the tool. It stops short of naming exclusions or pointing to search_exams/get_exam_details for other needs.

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