Skip to main content
Glama

Find trust centers

list_trust_centers
Read-onlyIdempotent

Lists IVERIOS trust centers you can query: those where you are an approved visitor (full access) and, with a query, public trust centers matching a company name or domain. Call this first to get the trust_center id for the other tools.

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

Input Schema

NameRequiredDescriptionDefault
queryNoCompany name or domain to search for (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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, so the safety profile is covered. The description adds real behavioral context beyond them: results are access-scoped to trust centers where the caller is an approved visitor, and a query widens the result set to public trust centers. Return volume and pagination behavior are not mentioned.

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, no filler. The access-scoping comes first and the call-ordering directive is placed at the end where it acts as the takeaway.

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 single optional-parameter read tool with full annotation coverage and no output schema, the description supplies what an agent needs: what is returned conceptually (trust centers with ids) and why to call it before other tools. Only the shape of the returned list (fields, whether ids are always present) is left implicit.

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 100% and the query parameter is already documented as an optional company name or domain. The description adds meaning the schema does not: supplying query switches from listing approved trust centers to searching public trust centers, and omitting it restricts results to full-access centers.

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?

The description opens with a specific verb and resource ("Lists IVERIOS trust centers") and immediately scopes the result set to two concrete categories: approved-visitor trust centers and public ones matched by query. It also distinguishes itself from the sibling listing tools by stating it produces the trust_center id they need.

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?

"Call this first to get the trust_center id for the other tools" gives explicit sequencing guidance relative to siblings like list_certificates and get_overview. The two operating modes (no query = your approved centers; with query = public centers) are spelled out, though there is no explicit when-not or failure guidance.

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