Skip to main content
Glama
lensesio

Lenses MCP Server

by lensesio
OverviewSchemaRelated ServersScoreDiscussions
Python

delete_kafka_connector

Remove a Kafka connector from a specified environment and cluster to manage data integration workflows.

Instructions

Deletes a Kafka connector.

Args: environment: The environment name. cluster: The cluster name. connector: The connector name.

Returns: The result of the delete operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
environmentYes
clusterYes
connectorYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/lenses_mcp/tools/kafka_connectors.py:150-168 (handler)
    The async handler function decorated with @mcp.tool() that implements the delete_kafka_connector tool. It constructs the DELETE API endpoint and executes the request via api_client.
    @mcp.tool()
async def delete_kafka_connector(
    environment: str,
    cluster: str,
    connector: str
) -> Dict[str, Any]:
    """
    Deletes a Kafka connector.
    
    Args:
        environment: The environment name.
        cluster: The cluster name.
        connector: The connector name.
    
    Returns:
        The result of the delete operation.
    """
    endpoint = f"/api/v1/environments/{environment}/proxy/api/kafka-connect/clusters/{cluster}/connectors/{connector}"
    return await api_client._make_request("DELETE", endpoint)
  • src/lenses_mcp/server.py:29-29 (registration)
    Top-level registration call that invokes the module registration function, which registers the delete_kafka_connector tool among others.
    register_kafka_connectors(mcp)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Deletes' implies a destructive mutation, it doesn't disclose critical behavioral traits: whether deletion is permanent/reversible, what permissions are required, if it affects related resources, or any rate limits. The description only states the basic action without safety or operational context.

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 concise with a clear purpose statement followed by Args and Returns sections. However, the Args section merely repeats parameter names without adding semantic value, and the structure could be more front-loaded with critical behavioral information instead of basic parameter listing.

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?

Given this is a destructive operation with no annotations, 3 undocumented parameters, and an output schema that presumably documents the return format, the description is incomplete. It lacks essential context: prerequisites, irreversible consequences, error conditions, and differentiation from sibling deletion tools. The output schema reduces need to explain returns, but other gaps remain significant.

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 only parameter names and types without meaning. The description adds minimal value by listing parameters in the Args section but doesn't explain what environments, clusters, or connectors are, their formats, or how to identify them. This partially compensates but leaves semantics unclear.

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 tool's purpose with a specific verb ('Deletes') and resource ('a Kafka connector'), making it immediately understandable. However, it doesn't explicitly differentiate from sibling tools like delete_sql_processor or delete_consumer_group, which would require mentioning it's specifically for Kafka connectors rather than other resources.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing to identify the connector first via list_kafka_connectors), when deletion is appropriate, or what happens after deletion. With multiple deletion tools in the sibling list, this lack of differentiation is a significant gap.

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