elasticsearch-mcp

by baburajr

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

close_pit

Read-only

Close an active point-in-time by its pit_id to release cluster resources after pagination is complete.

Instructions

Close a point-in-time by its pit_id to free cluster resources. Call after paging finishes.

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": {
      "pit_id": "<pit_id>"
    },
    "name": "close_pit"
  }
}

Input Schema

Name	Required	Description	Default
`pit_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

B3.4/5.0

Behavior1/5

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

Annotation Contradiction: the annotations declare readOnlyHint=true, while the description says the tool 'closes' a resource and 'frees cluster resources.' That is a state-changing behavior, not a read-only one. The description does not resolve or even acknowledge this mismatch, which can mislead an agent that trusts the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short, purposeful sentences. The primary action and effect are front-loaded, and the usage guidance is a compact follow-up with no filler or redundancy.

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?

For a single-parameter cleanup tool, this is nearly complete. It says what, why, and when. However, it omits required preconditions (the PIT must already be open) and the postcondition that the pit_id is no longer usable, and the annotation contradiction undermines overall completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents pit_id only as a required string with no description. The tool description adds 'by its pit_id,' which is almost a restatement. With schema description coverage at 0%, the description should explain how to obtain pit_id (e.g., from open_pit) and that it becomes invalid after closing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a concrete verb ('Close') and names a specific resource ('point-in-time'), scoped by pit_id, with a clear purpose ('free cluster resources'). It clearly reads as the terminal counterpart to open_pit and is not likely to be confused with search or query siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call after paging finishes' is an explicit, useful lifecycle instruction. It does not list alternative tools or exclusions, but the context of the sibling set (open_pit, paged_search) makes the intended workflow clear enough.

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