delete_topic
Delete a Kafka topic from the cluster using the control plane. This destructive action permanently removes the topic.
Instructions
destructive / control_plane / DELETE
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Delete a Kafka topic from the cluster using the control plane. This destructive action permanently removes the topic.
destructive / control_plane / DELETE
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description includes 'destructive' which hints at mutation, but does not disclose what exactly happens (e.g., permanent deletion, impact on producers/consumers). With no annotations, the description carries full burden but provides minimal information.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short but fails to convey essential purpose. Conciseness is not valuable when it omits necessary information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with no parameters, the description should at least state 'Deletes a topic'. It does not, leaving the agent to infer from the name alone.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, and schema coverage is 100% (empty schema). The description adds no param info, but baseline for zero params is 4. No extra value needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'destructive / control_plane / DELETE' is not a clear statement of what the tool does. It provides tags but not a verb+resource. The name suggests deletion, but the description is too vague to confirm.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like 'alter_topic_config' or 'create_topic'. No context on prerequisites or consequences.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vaquarkhan/kafka-mcp-enterprise-server-kip-1318'
If you have feedback or need assistance with the MCP directory API, please join our Discord server