keycloak-mcp-server

delete-client-scope

Delete a client scope in a Keycloak realm by specifying the realm and client scope ID. Use this to remove unwanted client scopes and clean up configuration.

Instructions

Delete a client scope

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>",
      "clientScopeId": "<clientScopeId>"
    },
    "name": "delete-client-scope"
  }
}

Input Schema

Name	Required	Description	Default
`realm`	Yes	Realm name
`clientScopeId`	Yes	Client scope ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Delete', implying destructiveness, but does not mention if the deletion is permanent, cascades to related entities, or requires special permissions. No side effects or error behavior are disclosed.

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

Conciseness3/5

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

The description is a single sentence with no wasted words, but it is under-specified. While concise, it lacks substantive details needed to understand the tool's behavior, making it minimally acceptable in structure.

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?

For a simple delete tool with two well-documented parameters, the description is adequate but not complete. It provides no context about side effects, prerequisites, or response expectations, and with no annotations or output schema, the agent is missing important information for a destructive operation.

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 fully documents both parameters (realm, clientScopeId) with 100% coverage. The description adds no additional semantic content about the parameters, so it meets the baseline for high schema coverage.

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 a client scope' is a direct restatement of the tool name, providing no additional nuance or distinction beyond the verb+resource. It does not add detail about what a client scope is or how this deletion differs from deleting other resources.

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 information is provided about when to use this tool, prerequisites, or alternative approaches. The description simply states the action without any context about use cases, permanence, or safer alternatives.

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

Deploy Server