elasticsearch-mcp

by baburajr

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

count_documents

Read-only

Count documents matching a query without returning hits. Size up a query result before carrying out the actual search.

Instructions

Count matching documents without returning hits. Cheap way to size a query before running it.

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>"
    },
    "name": "count_documents"
  }
}

Input Schema

Name	Required	Description	Default
`index`	Yes
`query`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark it read-only and non-destructive, and the description adds useful behavioral context: it returns no hits and is cheap to run. This goes beyond the annotations without contradicting them, though it does not describe edge cases like null query semantics or exact response shape.

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?

Two short sentences with no filler. The core behavior is front-loaded, and the secondary sentence provides a practical reason to use the tool without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, low-parameter tool backed by a readOnly annotation and an output schema, the description is mostly complete. The only meaningful gap is query parameter semantics, which is not provided by the schema description either.

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?

Schema description coverage is 0%, yet the description does little to explain the two parameters. 'Matching documents' implies query filtering, but the description does not clarify that query can be a string, object, or null, nor what a null query does or why the index parameter is required.

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 states a specific operation: counting matching documents. It also explicitly notes that it does not return hits, immediately distinguishing it from search-style sibling tools like paged_search or run_query.

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?

It gives a concrete use case: 'cheap way to size a query before running it,' which tells an agent when choosing this tool is appropriate. It does not explicitly list exclusions or alternatives, but the guidance is still clear.

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