Skip to main content
Glama

Give a domain API client a new secret

rotate_domain_client_secret
Destructive

Rotates a domain client's secret to replace a leaked credential. Issuing a new secret immediately invalidates the old one and all tokens it granted; the new secret is shown only once.

Instructions

Issues a new secret; the old one and every token it bought stop working at once. The new clientSecret is shown EXACTLY ONCE. For a leaked secret. 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": "rotate_domain_client_secret"
  }
}

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

A3.9/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true; the description adds substantial context beyond that: the old secret and every token it minted are invalidated immediately, and the new secret is displayed exactly once. The confirm=true gate is also stated. It does not cover permissions or rate limits, but the blast radius and irreversibility are well disclosed.

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?

Four short clauses, front-loaded with the action and its consequence, with the one-time secret warning capitalized for emphasis. No filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by explaining that the new clientSecret is shown exactly once, which is the key return-value fact. Combined with the invalidation warning and confirm gate, an agent has everything needed to call this destructive tool safely.

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 are already documented, including confirm's preview behavior. The description reinforces the confirm requirement and clarifies that the returned clientSecret is single-view, but adds little parameter meaning the schema lacks. 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?

States a specific verb and resource ("Issues a new secret" for a domain API client) and the title names the client explicitly, so it is distinguishable from rotate_domain_api_key and rotate_domain_signing_key. It stops short of naming those siblings directly, so differentiation relies on the reader inferring from the resource noun.

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?

"For a leaked secret" gives one clear triggering condition, which is real usage guidance. However, it offers no when-not guidance and does not point to the sibling rotation tools (api key, signing key) that an agent would need to choose between.

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