Skip to main content
Glama

Stop trusting an external token issuer

delete_trusted_issuer
Destructive

Remove a trusted issuer so its tokens are rejected on the next request; set confirm=true to execute.

Instructions

Removes a trusted issuer; its tokens are refused from the next request. Requires confirm=true.

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": "delete_trusted_issuer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe issuer's name on this domain, e.g. "auth0" — lowercase letters, digits, hyphens.
confirmNoMust be true to act. Omit/false returns a preview only.
domainIdYesThe domain's id — from list_domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the description earns credit for adding the effect timing (tokens refused from the very next request) and the confirm=true guard requirement. It does not state behavior on a missing issuer name, idempotency, or whether already-issued tokens are revoked elsewhere.

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 short clauses, zero filler, with the mutation and its effect front-loaded before the confirm requirement. Every sentence carries information an agent needs.

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 three-parameter destructive tool with full schema coverage and a destructiveHint annotation, the description supplies the missing pieces: what the removal actually does and that confirmation is mandatory. Only edge-case behavior (unknown issuer, partial state) is left unstated.

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 coverage is 100%, so all three parameters including the name format and the confirm preview behavior are already documented in the schema. The description's "Requires confirm=true" restates the schema rather than adding new meaning, so the baseline 3 applies.

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 a specific verb and resource ("Removes a trusted issuer") and adds the concrete consequence that its tokens are refused from the next request. It is distinguishable from set/check/list trusted-issuer siblings by implication, but never names them explicitly.

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: call this to stop trusting an issuer. There is no explicit when-to-use versus when-not guidance, no mention of the preview path as an alternative to committing, and no prerequisites such as required permissions.

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