Skip to main content
Glama

Check a trusted issuer or one of its tokens

check_trusted_issuer
Read-only

Check whether a trusted issuer is reachable and how many usable signing keys it publishes, or run a token through the gateway's validation to reveal the exact reason it is rejected.

Instructions

Without a token: fetches the issuer's keys now and says whether it is reachable and how many usable keys it publishes. With a token: runs it through exactly the gateway's check and says which check fails (token.audience_mismatch, token.expired…) or what a block would see as request.auth. The caller of an endpoint is only ever told invalid_token; this is where the reason is.

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": "<name>"
    },
    "name": "check_trusted_issuer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe issuer's name on this domain, e.g. "auth0" — lowercase letters, digits, hyphens.
tokenNoA token from the provider (a leading "Bearer " is fine).
domainIdYesThe domain's id — from list_domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true, and the description stays consistent while adding real depth: it performs a live key fetch ('now'), mirrors the gateway's exact validation path, names concrete failure codes (token.audience_mismatch, token.expired), and explains it also shows what a block would see as request.auth. That is diagnostic behavior an agent could not infer from the annotation.

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 tightly packed sentences, each front-loaded with its mode ('Without a token...', 'With a token...'), followed by one sentence of motivation. No filler and no repetition of the title.

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 no output schema, the description carries the burden of describing results, and it does so qualitatively for both modes (reachability, key count, failing check, request.auth view). It never sketches the response shape, so an agent knows what it will learn but not exactly what it will receive.

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%, so the baseline is 3, but the description adds the meaning the schema omits: the optional token parameter switches the entire behavior between a reachability probe and a token validation. It does not add format detail beyond the schema's own note about a leading 'Bearer '.

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 gives a specific verb and resource for both operating modes: without a token it fetches the issuer's keys and reports reachability and usable key count; with a token it runs the gateway's own check and reports the failing check. That distinguishes it immediately from the set/delete/list trusted-issuer siblings.

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?

It clearly states the two conditions that select each mode and gives a strong reason to reach for it: endpoint callers only ever see invalid_token, so this is the tool that surfaces the actual reason. It stops short of naming sibling tools or stating when not to use it, so it is clear context rather than explicit routing.

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