Skip to main content
Glama

skycloak_update_realm_group

Idempotent

Rename a realm group within a managed Keycloak cluster to organize and update access structures.

Instructions

Rename a realm group.

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>",
      "group_id": "<group_id>",
      "name": "<name>"
    },
    "name": "skycloak_update_realm_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesthe new group name
realmYesthe Keycloak realm name
group_idYesthe group ID
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that — no note on whether the old name is released, whether the group ID changes, or what permissions are required for a rename.

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?

A single front-loaded sentence with zero waste. It is arguably too terse rather than padded, so it scores well on structure but not perfectly on informativeness.

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 and full annotation set exist, so the description needn't explain return values or safety. However, for a mutation tool it leaves the agent without any behavioral context about the rename operation itself, which is a modest gap.

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%, so all four parameters (cluster_id, realm, group_id, name) are already documented in the schema. The description adds no extra meaning, which is the baseline expectation when the schema does the work.

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 ("Rename a realm group"), which is precise enough to distinguish it from create/delete/get siblings. Minor friction: the tool name says "update" while the description says "rename", though the schema's single `name` parameter supports the narrower reading.

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 on when to use this versus skycloak_update_realm or the other update_* siblings, and no prerequisites or exclusions stated. The agent must infer usage entirely from the name.

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