Skip to main content
Glama
Faust-Systems

keycloak-mcp

Ensure hardcoded claim mapper

ensure_hardcoded_claim_mapper

Idempotently ensure a Keycloak client includes a hardcoded claim in tokens. Matches existing mappers by claim name; reports plan or applies changes on write=true.

Instructions

Idempotently ensure a client has an oidc-hardcoded-claim-mapper emitting the given claim. Matches existing mappers by claim name: reports 'already-present' when the config matches, a diff + update when it differs, and a create when absent. With write=false (default) it only returns the plan; write=true applies it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostYesTarget Keycloak host key, as configured in the config file's "hosts" map (or the KC_<HOST>_* env fallback). A host whose "production" flag is true, or absent, is treated as PRODUCTION and its writes are gated by "allowProdWrite".
realmYesTarget realm name for the operation.
writeNofalse (default) = dry run: report what would happen without changing anything. true = apply the change. Production hosts additionally require KC_ALLOW_PROD_WRITE=true in the server environment.
clientIdYesThe client's clientId (the human-readable OAuth client id, not the UUID).
claimNameYesThe claim key to emit in tokens, e.g. "realm".
claimValueYesThe hardcoded value the claim should carry.
addToIdTokenNoWhether the claim is added to ID tokens (default false).
claimJsonTypeNoKeycloak claim JSON type label (default "String").String
addToAccessTokenNoWhether the claim is added to access tokens (default true).
Behavior4/5

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

It discloses idempotent behavior, dry-run capability, and how it handles existing mappers (match, diff, create). Missing permission or side-effect details, but no annotations exist to supplement.

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 sentences, highly concise, front-loaded with key behavior. Every sentence earns its place with no fluff.

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?

Given the complexity (9 params, no output schema, no annotations), the description covers idempotency, matching logic, and dry-run. However, it lacks mention of return format or error handling, which would enhance completeness.

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 baseline is 3. The description adds overall context but does not provide additional meaning for individual parameters beyond what the schema already offers.

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?

The description clearly states the tool ensures a client has a specific oidc-hardcoded-claim-mapper, using the verb 'ensure' and specifying the resource. It distinguishes itself from siblings like delete_protocol_mapper or list_protocol_mappers by its idempotent create-or-update behavior.

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

Usage Guidelines4/5

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

The description explains the purpose and dry-run vs apply behavior, but does not explicitly state when not to use or list alternative tools. However, the context from sibling tools provides implied differentiation.

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/Faust-Systems/keycloak-mcp'

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