Skip to main content
Glama

Open Agent Guide

List Compliance Certifications

list_compliance_certifications
Read-onlyIdempotent

List compliance certifications (e.g. SOC 2, ISO 27001, HIPAA), optionally narrowed by search across names, verbose names, and slugs. Use this to resolve the opaque compliance_certification_ids that get_product returns to named certifications, and to enumerate which certifications the catalog tracks.

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

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor from a previous page's response.
searchNoFree-text search across names, slugs, and text.
page_sizeNoResults per page (1-100).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety and idempotency profile is fully covered structurally. The description adds some data-shape context (that IDs are opaque and require resolution), but says nothing about result volume, pagination expectations, or whether the catalog list is stable.

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?

Two sentences, zero filler, with the resource definition front-loaded before the search narrowing and the use-case guidance. Every clause contributes either disambiguation or routing value.

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 needn't explain return values, and annotations handle the safety profile, so it is largely complete. The only minor gap is that paging behavior (how to continue via cursor) is left entirely to the schema rather than being reinforced in prose.

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%, so cursor, search, and page_size are already documented, which sets the baseline at 3. The description adds a small amount by noting search spans names, verbose names, and slugs (slightly richer than the schema's "names, slugs, and text"), but supplies no syntax, matching semantics, or pagination workflow guidance.

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 ("List compliance certifications") and grounds it with concrete examples (SOC 2, ISO 27001, HIPAA), so the agent knows exactly what domain object is being enumerated. It is clearly distinguishable from siblings like get_product and list_capabilities, which cover different resource types.

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

Usage Guidelines5/5

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

Gives two explicit use cases: resolving the opaque compliance_certification_ids returned by get_product into names, and enumerating which certifications the catalog tracks. Naming the sibling whose output feeds this tool is exactly the routing guidance an agent needs to chain the two calls correctly.

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