Skip to main content
Glama
Sign In
keycloak-mcp-server

keycloak-mcp-server

by thebylito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

update-realm

Update Keycloak realm settings, including enabled status and display name, to adjust configuration as needed.

Instructions

Update realm settings and configurations

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": {
      "realm": "<realm>"
    },
    "name": "update-realm"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesRealm name
enabledNoEnabled status
displayNameNoDisplay name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Update realm settings and configurations,' which implies a write operation but does not disclose side effects, permission requirements, reversibility, or impact on existing settings.

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?

The description is one short sentence, front-loaded with the action and resource. There is no filler, but the brevity sacrifices detail.

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

Completeness2/5

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

With no annotations or output schema, the description is too minimal to be complete. It does not clarify whether partial updates are supported (e.g., whether omitting optional fields resets them), what response to expect, or any prerequisites. This is a simple tool but the description leaves important gaps.

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?

The input schema has 100% description coverage for all three parameters, so the baseline is 3. The description adds no additional semantics beyond the schema.

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?

The description states the tool updates realm settings and configurations, using a specific verb and resource. It clearly differentiates from sibling update tools targeting other resources (e.g., update-client, update-role) but does not enumerate which settings beyond the schema, so it is clear but not fully distinguishing.

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 guidance is provided on when to use this tool vs alternatives like get-realm-settings or create-realm. There is no mention of prerequisites, exclusions, or preferred scenarios.

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