Skip to main content
Glama

List a domain's trusted issuers

list_trusted_issuers
Read-only

Lists external identity providers whose tokens a domain's JWT or API-key/JWT endpoints accept, along with accepted scope claims and algorithms.

Instructions

Lists the external identity providers (Auth0, Okta, Entra, Cognito, Firebase, Keycloak…) whose tokens the domain's jwt / apiKeyOrJwt endpoints accept, with the accepted scope claims and algorithms.

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": {
      "domainId": "<domainId>"
    },
    "name": "list_trusted_issuers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYesThe domain's id — from list_domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already declares the safety profile, so the description's job is to add context, which it does by disclosing the shape of the returned data (issuers plus accepted scope claims and algorithms). It does not mention pagination, ordering, or behavior when a domain has no configured issuers, so the transparency is useful but not 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?

One front-loaded sentence that leads with the verb and resource, then qualifies with endpoint types and returned fields. The parenthetical vendor list (Auth0, Okta, Entra, Cognito, Firebase, Keycloak…) is slightly verbose but usefully conveys coverage; nothing else is wasted.

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-parameter read-only list with no output schema, the description does the essential work: it names the resource, the endpoint scope, and the fields an agent will receive. Only edge-case behavior (empty results, size limits) is left unstated, which is minor at this complexity.

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 parameter is fully described in the schema, including the cross-reference to list_domains for obtaining the id. The description only restates 'the domain's' endpoints, adding no scoping or format detail beyond what the schema provides — baseline 3 given 100% coverage.

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 (lists) and a specific resource (external identity providers whose tokens the domain's jwt/apiKeyOrJwt endpoints accept), plus the enumerated content of each entry (scope claims and algorithms). An agent can distinguish this from list_domain_api_keys or list_runner_clients without opening any schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the mention of jwt / apiKeyOrJwt endpoints tells the agent this is an inspection tool for JWT auth configuration, but there is no explicit 'use when / don't use when' guidance. Alternatives such as check_trusted_issuer (single-entry lookup) or set_trusted_issuer (mutation) are available in the catalog but never referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.