Skip to main content
Glama
Sign In
Elasticsearch/OpenSearch MCP Server

Elasticsearch/OpenSearch MCP Server

by Rbedoyag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_document

Remove a specific document from an Elasticsearch or OpenSearch index using its unique ID to manage data and maintain index integrity.

Instructions

        Delete a document by ID.
        
        Args:
            index: Name of the index
            id: Document ID

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": {
      "index": "<index>",
      "id": "<id>"
    },
    "name": "delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.6

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Delete') but doesn't mention permissions needed, whether deletion is permanent, error handling, or other behavioral traits like rate limits or side effects.

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 two-sentence structure is efficient, though the parameter list could be integrated more seamlessly rather than as a separate 'Args:' section.

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 complexity of a deletion tool with no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks crucial details like confirmation prompts, return values, error conditions, or integration with sibling tools.

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 description must compensate. It lists the parameters ('index' and 'id') with brief explanations, adding some meaning beyond the schema. However, it doesn't fully detail constraints or examples, leaving gaps in understanding.

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 ('document by ID'), making the purpose specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'delete_index' or 'delete_by_query', which would require a 5.

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 like 'delete_by_query' or 'delete_index'. The description only states what the tool does, not the context or prerequisites for its use.

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