Skip to main content
Glama
Sign In
Elasticsearch MCP Server

Elasticsearch MCP Server

by cr7258
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_aliases

Retrieve and display all aliases in an Elasticsearch cluster to manage index routing and naming.

Instructions

List all aliases.

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_aliases"
  }
}

Input Schema

NameRequiredDescriptionDefault
clusterNoOptional cluster name. Uses the default cluster if omitted.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.4
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / cluster / description
      Added value: +"Optional cluster name. Uses the default cluster if omitted."
  2. Addedv2.1.2
  3. Removedv2.1.1
  4. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and 'List' at least implies a non-mutating read. However, it says nothing about required permissions, cluster scoping behavior when the cluster arg is omitted, or result size, so the behavioral profile remains thin.

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?

A single front-loaded sentence with zero filler. It is efficiently structured, though its brevity borders on under-specification rather than optimal conciseness.

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?

The tool is simple, takes no required parameters, and has an output schema so return values need not be explained. Still, the description leaves the cluster-scoping behavior and the distinction from get_alias unaddressed.

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 100% and the single 'cluster' parameter is fully documented in the schema, including the default-cluster fallback. The description adds nothing about it, so the baseline 3 applies.

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?

States a specific verb (List) and resource (aliases) with an explicit 'all' scope, so the operation is unambiguous. It does not distinguish itself from the sibling get_alias, which fetches a single alias, so an agent gets no routing signal beyond the name.

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 when-to-use guidance, no prerequisites, and no mention of the alternative get_alias for single-alias lookups. The agent must infer the choice purely from the tool name.

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