Skip to main content
Glama
mrz1880

mcp-keycloak-admin

Get client secret

keycloak_client_get_secret
Read-onlyIdempotent

Get the current secret of a confidential Keycloak client. Returns masked secret by default; pass reveal=true for plaintext.

Instructions

Read the current secret of a confidential (non-public) realm client. Read-only and idempotent; it does not change the secret. By default the secret is returned masked; pass reveal=true to return the plaintext value. Use keycloak_client_get to confirm a client is confidential first, and keycloak_client_regenerate_secret to rotate it. Returns the (masked or plaintext) secret string, or "Client not found." when no client matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
revealNoWhen true, return the plaintext secret; when false or omitted (default), return a masked value. Set to true only when the caller actually needs the raw secret.
clientIdYesThe client's clientId (the human-readable OAuth/OIDC client identifier, e.g. "my-app"), not the internal UUID. Required. The client must be confidential (publicClient=false) to have a secret.
Behavior5/5

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

Annotations declare read-only and idempotent; description adds that secret is masked by default and returns plaintext only with reveal=true. Notes return value format and error case for missing client.

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 sentences, front-loaded with main purpose. No unnecessary words.

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?

Given 2 params and no output schema, description adequately explains behavior, return values, and error case. Sibling tools are listed but no further context needed.

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 covers both parameters fully (100%). Description adds context: clientId vs UUID, confidentiality requirement, and reveal parameter effect.

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?

Clear verb 'Read' and specific resource 'current secret of a confidential realm client'. Differentiates from sibling tools like keycloak_client_get (client info) and keycloak_client_regenerate_secret (rotation).

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?

Explicitly instructs to use keycloak_client_get first to confirm confidentiality, and mentions keycloak_client_regenerate_secret for rotation. Also advises on when to set reveal=true.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrz1880/mcp-keycloak-admin'

If you have feedback or need assistance with the MCP directory API, please join our Discord server