Skip to main content
Glama

Delete a domain API client

delete_domain_client
Destructive

Permanently deletes a domain client and refuses its tokens on later requests; requires confirm=true. Omit or set confirm=false to preview only.

Instructions

Permanently deletes a client; its tokens are refused from the next request. update_domain_client active:false is the reversible way. 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>",
      "clientId": "<clientId>"
    },
    "name": "delete_domain_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to act. Omit/false returns a preview only.
clientIdYesThe client's id ("dcl_…") — from list_domain_clients.
domainIdYesThe domain's id — from list_domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the safety profile is known; the description adds genuine consequence detail beyond that – permanence and immediate token refusal from the next request. It stops short of saying whether related API keys or secrets are also removed, which leaves one meaningful behavioral gap.

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?

Three short clauses, front-loaded with the destructive nature and the consequence before the safety alternative. Every clause carries information, though the confirm requirement duplicates the schema rather than earning its place.

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 no-output-schema destructive tool, it covers permanence, the observable effect on tokens, the reversible alternative, and the confirmation gate. The only real omission is the blast radius – whether subordinate API keys or previously issued secrets are also destroyed.

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% and the schema already states that confirm must be true and that omitting it returns a preview, so the description's 'Requires confirm=true' is essentially a restatement. No additional meaning is added for domainId or clientId beyond what the schema supplies.

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 ('Permanently deletes a client') and immediately scopes the effect ('its tokens are refused from the next request'), so an agent can distinguish it from update_domain_client or revoke_domain_client_tokens 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 Guidelines5/5

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

Names the explicit alternative ('update_domain_client active:false is the reversible way') and the condition that selects it, plus the hard precondition 'Requires confirm=true'. This is exactly the when/when-not guidance an agent needs before a destructive call.

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