keycloak-mcp-server

create-client-scope

Create a client scope in a Keycloak realm to define and manage token scopes. Specify realm, name, protocol, and attributes to control token claims.

Instructions

Create a new client scope (CRITICAL for managing token scopes)

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

Input Schema

Name	Required	Description
`name`	Yes	Client scope name
`realm`	Yes	Realm name
`protocol`	No	Protocol (e.g., openid-connect)
`attributes`	No	Client scope attributes
`description`	No	Client scope description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations present, the description carries the full burden of disclosing behavior. It only states that it creates a client scope and hints at its role in token scopes, but does not mention side effects, authorization requirements, idempotency, or error behavior (e.g., duplicate name). This is a significant gap for a create operation.

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 a single sentence and front-loaded with the core action. The parenthetical 'CRITICAL for managing token scopes' adds a bit of context but could be seen as slightly dramatic; still, it is concise and no words are wasted. It earns a 4 for efficiency.

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 create operation with 5 parameters (2 required), no output schema, and no annotations, the description is under-specified. It gives no information about return values, prerequisites (e.g., realm must exist), or special constraints. An agent would need to infer too much about how to correctly invoke it.

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% (all 5 parameters have descriptions). The description text adds no additional meaning beyond the schema, so the baseline of 3 applies. It does not clarify required fields, uniqueness constraints, or format expectations beyond what the schema already provides.

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's action: 'Create a new client scope'. The verb 'create' and resource 'client scope' are specific, and it distinguishes itself from sibling tools like update-client-scope and delete-client-scope by focusing on creation. The parenthetical adds relevant context about token scopes.

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 versus alternatives. It does not mention that this is for new scopes, that update-client-scope should be used for modifications, or any prerequisites such as an existing realm. The sibling list exists but the description does not reference it.

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

Deploy Server