Skip to main content
Glama
elasticsearch-mcp

elasticsearch-mcp

list_indices

Read-only

List Elasticsearch indices matching a pattern such as logs-* and return health, status, document count, and size for inspection.

Instructions

List indices matching a pattern such as "logs-*" or "a,b", with health, status, doc count and size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_indices"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNo*

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already establishes the safety profile, so the description's contribution is the disclosure that results carry health, status, doc count and size — valuable given no output schema exists. It stops short of stating whether the default "*" returns every index, whether hidden/system indices are included, or whether results are capped.

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?

One sentence, front-loaded with the action and resource, with the return fields appended as a compact clause. Nothing is redundant and nothing padding-like.

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 optional-parameter read tool with no output schema, the description covers the returned fields and pattern syntax reasonably well. It leaves notable gaps around default behavior when no pattern is supplied and result-size or pagination behavior, which matter for a listing call against a large cluster.

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

Parameters4/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 carry parameter meaning, and it does by demonstrating two concrete pattern syntaxes: glob wildcards ("logs-*") and comma-separated lists ("a,b"). It does not mention that the parameter defaults to "*" and is optional, so omitting it silently lists everything.

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?

A specific verb plus resource ("List indices") with the filtering scope and the returned fields named, so the agent knows exactly what comes back. It does not differentiate itself from siblings such as get_mappings or cluster_health, leaving the agent to infer which is appropriate for index-level metadata.

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

Usage Guidelines3/5

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

Usage is only implied through pattern examples ("logs-*", "a,b"), which show the intended shape of a call but not when to choose this over get_mappings or search. There are no exclusions, prerequisites, or statements about what happens with no matching indices.

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