Skip to main content
Glama
elasticsearch-mcp

elasticsearch-mcp

cluster_health

Read-only

Check Elasticsearch cluster status, node count, and shard counts to monitor health and detect green, yellow, or red states.

Instructions

Cluster health: status (green, yellow or red), node count and shard counts.

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": "cluster_health"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description's real contribution is the return shape (status colors, node count, shard counts), which substitutes for the absent output schema. It says nothing about scope (which cluster/connection it reports on) or failure behavior, so it adds useful but limited context.

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 compact sentence with the resource front-loaded and the reported values enumerated. Slightly fragmentary style, but every clause carries information and nothing is wasted.

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 zero-param, annotation-covered read tool with no output schema, describing the returned fields is close to sufficient. The main omission is scope — which cluster or connection the health applies to — but little else is needed to call it correctly.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing parameters.

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?

Names a specific resource ('Cluster health') and enumerates what it reports: status with the green/yellow/red vocabulary, node count, and shard counts. The verb is implicit (a health read), but the subject is unambiguous and distinguishable from siblings like get_shards or list_indices, which target specific objects rather than overall health.

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 exclusions, and no reference to any sibling tool. An agent must infer that this is the high-level health check to try before drilling into get_shards or search.

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