Skip to main content
Glama

List certificates

list_certificates
Read-onlyIdempotent

The ICO certificates: name, kind (exam or role), issuer, description, the course slugs that lead to each, url.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description's contribution is the return payload shape (name, kind, issuer, description, course slugs, url), which is genuinely useful since no output schema exists, but it says nothing about volume, ordering, or whether the list is complete.

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?

A single compact clause with zero filler, and the resource is front-loaded before the field enumeration. It is a noun-phrase fragment rather than a sentence with a verb, which is terse but slightly less scannable than an action-first phrasing.

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 one-optional-parameter listing tool with no output schema, the description supplies the key missing piece: the shape of the returned records, including the exam/role distinction and the course-slug linkage. It stops short of covering pagination or result size, which is a minor gap for a catalog listing.

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?

The single 'lang' parameter has 100% schema description coverage including the enum values and default, so the schema does all the work. The description adds no further meaning about how lang affects the returned fields (e.g. whether name/description are translated), which is the one piece of parameter context that would have helped.

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?

The description names the concrete resource (ICO certificates) and enumerates its fields, so an agent can tell this returns certificate records rather than blog posts, events, or courses. It never states the operation as a verb ('list') and does not explicitly distinguish itself from siblings like search_courses, which keeps it below a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all: no statement about when to call this versus list_topics/list_trainers or whether this is the full unfiltered catalog. The only usage hint is implicit in the field listing (course slugs suggest a join to get_course), and nothing tells the agent 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