Skip to main content
Glama
lensesio

Lenses MCP Server

by lensesio

delete_consumer_group

Remove a specific consumer group from a Kafka environment to manage cluster resources and maintain system organization.

Instructions

Delete a consumer group.

Args: environment: The environment name. group_id: The ID of the consumer group to delete.

Returns: The result of the delete operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentYes
group_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function implementing the 'delete_consumer_group' MCP tool. It deletes a Kafka consumer group by making a DELETE API request.
    @mcp.tool()
    async def delete_consumer_group(environment: str, group_id: str) -> Dict[str, Any]:
        """
        Delete a consumer group.
        
        Args:
            environment: The environment name.
            group_id: The ID of the consumer group to delete.
        
        Returns:
            The result of the delete operation.
        """
        endpoint = f"/api/v1/environments/{environment}/proxy/api/consumers/{group_id}"
        return await api_client._make_request("DELETE", endpoint)
  • Calls the registration function to register the Kafka consumer groups tools, including 'delete_consumer_group', with the MCP server.
    register_kafka_consumer_groups(mcp)
  • Imports the registration function for Kafka consumer groups tools.
    from tools.kafka_consumer_groups import register_kafka_consumer_groups
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Delete a consumer group' but doesn't disclose critical behavioral traits such as whether this is destructive, irreversible, requires specific permissions, has side effects, or what happens to associated data. This is inadequate for a mutation tool with zero annotation coverage.

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 appropriately sized and front-loaded with the core action. The Args and Returns sections are structured, but the Returns statement ('The result of the delete operation') is vague and could be more informative, slightly reducing efficiency.

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?

Given the tool's complexity as a deletion operation with no annotations and an output schema (implied by 'Has output schema: true'), the description is moderately complete. It covers the basic action and parameters but lacks behavioral context and detailed usage guidelines, which are crucial for safe tool 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 0%, so the schema provides no parameter details. The description adds minimal semantics by naming the parameters ('environment' and 'group_id') and briefly describing them, but it doesn't explain format, constraints, or examples. This partially compensates but leaves significant gaps.

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 clearly states the verb ('Delete') and resource ('a consumer group'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'delete_consumer_group_offsets' or 'delete_consumer_group_topic_partition_offset', which also delete aspects of consumer groups.

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. With siblings like 'delete_consumer_group_offsets' and 'delete_consumer_group_topic_partition_offset', the description lacks context on whether this deletes the entire group or specific parts, leaving the agent uncertain about tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lensesio/lenses-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server