AKHQ MCP Server

get_group_acls

Read-onlyIdempotent

Retrieve access control lists (ACLs) for a specific consumer group in a Kafka cluster. Provide the cluster and consumer group name to inspect permissions.

Instructions

Get ACLs for a consumer 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": "<cluster>",
      "groupName": "<groupName>"
    },
    "name": "get_group_acls"
  }
}

Input Schema

Name	Required	Description	Default
`cluster`	Yes	Cluster name
`groupName`	Yes	Consumer group name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description is consistent with that. It adds no additional behavioral context such as pagination, authentication, or error behavior, but it does not contradict the annotations.

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 short sentence with no filler or redundancy. It front-loads the verb and object, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read tool with complete schema descriptions and safety annotations, the description is nearly sufficient. It lacks an explicit return format or usage boundaries, but nothing essential blocks correct invocation.

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 both cluster and groupName described. The description adds little beyond mapping 'consumer group' to the groupName parameter, which aligns with the baseline expectation when the schema already documents the parameters.

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?

The description uses a specific verb ('Get') and names the resource ('ACLs for a consumer group'), which clearly indicates this tool fetches group-scoped ACLs rather than cluster- or topic-scoped ones. It does not explicitly name sibling alternatives, so it doesn't score a full 5, but the resource scoping is clear.

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 over alternatives such as get_acls, get_acls_by_principal, or get_topic_acls. The intended use case is only implied by the resource phrase and is not explicitly stated.

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

Deploy Server