Skip to main content
Glama
cr7258

Elasticsearch MCP Server

delete_index

Remove an Elasticsearch index to free storage space and manage cluster resources by specifying the index name.

Instructions

        Delete an index.
        
        Args:
            index: Name of the index
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYes

Implementation Reference

  • The MCP tool handler function for 'delete_index'. It is decorated with @mcp.tool() and delegates the deletion to the underlying search client.
    @mcp.tool()
    def delete_index(index: str) -> Dict:
        """
        Delete an index.
        
        Args:
            index: Name of the index
        """
        return self.search_client.delete_index(index=index)
  • The underlying client method implementation that performs the actual index deletion using the Elasticsearch/OpenSearch client.
    def delete_index(self, index: str) -> Dict:
        """Delete an index."""
        return self.client.indices.delete(index=index)
  • src/server.py:41-53 (registration)
    Registration of IndexTools (containing delete_index) via ToolsRegister.register_all_tools during server initialization.
    register = ToolsRegister(self.logger, self.search_client, self.mcp)
    
    # Define all tool classes to register
    tool_classes = [
        IndexTools,
        DocumentTools,
        ClusterTools,
        AliasTools,
        DataStreamTools,
        GeneralTools,
    ]        
    # Register all tools
    register.register_all_tools(tool_classes)
  • Configuration marking 'delete_index' as a high-risk operation for IndexTools, which can conditionally disable its registration.
    HIGH_RISK_OPERATIONS = {
        "IndexTools": {
            "create_index",
            "delete_index",
        },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool deletes an index but doesn't mention critical aspects like whether this is reversible, requires specific permissions, affects data, or has rate limits. This is inadequate for a destructive operation.

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 brief and front-loaded with the core purpose, followed by parameter details. It avoids unnecessary words, though the formatting with extra whitespace slightly reduces efficiency. Overall, it's appropriately sized for a simple tool.

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 the tool's destructive nature, lack of annotations, no output schema, and low schema coverage, the description is incomplete. It fails to address safety, outcomes, or error handling, leaving significant gaps for an AI agent to use it correctly.

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?

The description adds minimal semantics by naming the parameter ('index') and indicating it's the name of the index to delete. With 0% schema description coverage and 1 parameter, this provides basic clarification but doesn't compensate fully for the schema gap, meeting the baseline for low coverage.

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 action ('Delete') and target resource ('an index'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar deletion tools like 'delete_data_stream' or 'delete_document' among the siblings, preventing a perfect score.

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 like 'delete_data_stream' or 'delete_by_query'. It lacks context about prerequisites, consequences, or typical use cases, offering only basic usage instructions.

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/cr7258/elasticsearch-mcp-server'

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