Skip to main content
Glama

Certificates

list_certificates
Read-onlyIdempotent

Certifications (e.g. ISO/IEC 27001, SOC 2) with status, issuer, accreditation, issue/expiry dates, scope and the certificate document if available.

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": {
      "trust_center": "<trust_center>"
    },
    "name": "list_certificates"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOptional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
trust_centerYesTrust center id (from list_trust_centers), its domain or the exact company name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral detail beyond that — the certificate document is included only "if available" — but says nothing about pagination, ordering, or how results differ across trust centers.

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?

A single sentence, front-loaded with the resource type and followed by a compact enumeration of returned fields. There is no filler, hedging, or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with rich annotations, most of the burden is already carried by structured fields. However, with no output schema, the description is the only source of return-shape information, and it gives a flat field list without indicating collection structure, cardinality, or whether documents are returned as links versus extracted text.

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 100%, with both the trust_center identifier (id, domain, or exact company name) and the optional language code fully documented inline. The description adds no additional meaning about either parameter, so the baseline of 3 is appropriate.

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 resource precisely ("Certifications (e.g. ISO/IEC 27001, SOC 2)") and enumerates the attributes it carries, so an agent knows exactly what data it surfaces. It never states a verb ("list") and gives no signal distinguishing it from siblings like list_documents or list_subprocessors, which is the only thing keeping it from 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, no when-not-to-use guidance, and no alternative named. The description also never says that a trust center identifier is required, so an agent must read the schema to learn that this tool cannot be called standalone.

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