Skip to main content
Glama

skycloak_rotate_application_secret

Destructive

Regenerate an application's client secret in a Keycloak realm and return the new value once, enabling credential rotation after exposure or policy changes.

Instructions

Regenerate an application's client secret and return the new value (shown only once).

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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "client_id": "<client_id>"
    },
    "name": "skycloak_rotate_application_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
client_idYesthe application client ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
client_secretYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the risk profile is known. The description adds one genuinely valuable fact beyond that: the new secret is returned and shown only once, so it cannot be re-read later. However, it omits the key consequence of a rotation — whether the previous secret is immediately invalidated and breaks existing clients — and says nothing about auth requirements.

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?

A single front-loaded sentence with the action first and the critical 'shown only once' caveat attached to the return value. Every clause earns its place with no filler.

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

Completeness3/5

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

An output schema exists, so return-value detail is not required, yet the description still usefully flags the one-time visibility of the secret. For a destructive, non-idempotent mutation it is still thin: the irreversibility of the rotation and its effect on already-deployed clients are the things an agent most needs and they are absent.

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% (realm, client_id, cluster_id each documented), so the schema already carries parameter meaning and the baseline is 3. The description adds no syntax, format, or selection hints beyond what the schema provides.

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 ('Regenerate an application's client secret') plus the return behavior, so it is distinguishable from siblings like skycloak_update_application or skycloak_get_application. It does not explicitly name which sibling to use instead, which keeps it out of the top band.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given; nothing says to prefer this over skycloak_update_application for credential changes, or what prerequisites (permissions, cluster/realm state) must hold. The only hint is the parenthetical 'shown only once', which implies the caller should persist the value but is not framed as usage guidance.

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

Deploy Server

Other Tools