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

keycloak-mcp-server

by thebylito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete-role

Deletes a role from a Keycloak realm. Provide realm, role name, and client ID when removing a client role.

Instructions

Delete roles

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>",
      "roleName": "<roleName>"
    },
    "name": "delete-role"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesRealm name
clientIdNoClient ID for client roles
roleNameYesRole name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2/5.0
Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it reveals nothing beyond the name. It does not mention side effects (e.g., cascading removal from composites), reversibility, or permissions, and the plural 'roles' is misleading given a singular roleName.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is under-specified, consisting of a two-word phrase that restates the tool name. While short, it lacks any structural detail that would help an agent understand scope or usage, making it minimally viable at best.

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?

For a delete tool with an optional clientId and no output schema or annotations, the description is incomplete. It fails to clarify the distinction between deleting realm roles and client roles, or what happens to dependent entities, leaving significant gaps for an agent.

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 the baseline is 3. The description adds no meaning beyond the schema fields; the optional clientId and its role in targeting client roles remain unexplained in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete roles' is essentially a restatement of the tool name 'delete-role' with no added specificity, failing to distinguish it from sibling tools like delete-role-by-id or delete-composite-roles. It does not mention whether it handles realm roles, client roles, or both.

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 usage guidance is provided. The description gives no indication of when to use this tool versus other delete tools, nor does it explain the optional clientId parameter for client roles or any prerequisites.

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