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

keycloak-mcp-server

by thebylito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list-composite-group-roles

Retrieve composite roles for a group in Keycloak by providing realm and group ID. Get a complete list of effective roles, including inherited ones.

Instructions

List composite roles for a 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": {
      "realm": "<realm>",
      "groupId": "<groupId>"
    },
    "name": "list-composite-group-roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesRealm name
groupIdYesGroup ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'List', implying a read operation, but does not reveal permissions, response format, pagination, or whether composite roles are directly assigned or inherited. This minimal disclosure adds little beyond the tool's name.

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

Conciseness5/5

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

The description is a single, focused sentence with no redundant words. It is concise and front-loaded, earning its place without unnecessary elaboration.

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?

The description is too brief for a domain-specific tool. It does not explain what 'composite roles' are, how they relate to groups, or how the response differs from similar tools. No output schema exists, so the description should provide more context, but it leaves the agent with ambiguity.

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% with descriptions for both 'realm' and 'groupId'. The tool description adds no additional parameter semantics, but since the schema already documents parameters, the baseline of 3 applies. No examples or format details are provided.

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 'List composite roles for a group' uses a specific verb ('List') and resource ('composite roles for a group'), clearly distinguishing it from sibling tools like 'list-available-group-roles' or 'get-group-roles'. The scope is explicit, making the purpose unambiguous.

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 alternative role-listing tools. The description does not mention any context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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