Skip to main content
Glama
Sign In
AKHQ MCP Server

AKHQ MCP Server

by seb-noirot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_group_topics

Read-onlyIdempotent

Retrieve the list of topics consumed by a specific consumer group in a Kafka cluster. Provide the cluster name and consumer group name to get the topics.

Instructions

Get topics 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_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterYesCluster name
groupNameYesConsumer group name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the useful scoping fact that the result is topics for a consumer group, but it does not disclose return format, ordering, pagination, or error behavior.

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, front-loaded sentence with no filler. Every word contributes to the meaning, and the core action and resource are immediately clear.

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-only lookup with robust annotations and no output schema, the description is nearly complete. 'Get topics' reasonably implies the return value, and the schema covers all required parameters; only explicit return-shape wording is missing.

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 'Cluster name' and 'Consumer group name' already documented in the input schema. The description does not add additional meaning beyond what the schema already provides, so the baseline score of 3 applies.

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 states a specific action, 'Get topics', and a specific resource, 'for a consumer group', which clearly distinguishes this from broader tools like get_topics or other group-level tools like get_group_members and get_group_offsets. It does not explicitly name a sibling, but the scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrasing implies this tool should be used when an agent needs the topics associated with a particular consumer group. However, it provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives such as get_groups or get_group_by_name.

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