Skip to main content
Glama
Sign In
Elasticsearch 7.x MCP Server

Elasticsearch 7.x MCP Server

by imlewc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

es-info

Retrieve Elasticsearch cluster information and configuration details from the MCP server for monitoring and troubleshooting database operations.

Instructions

Get Elasticsearch info

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": {
      "req": "<req>"
    },
    "name": "es-info"
  }
}

Input Schema

NameRequiredDescriptionDefault
reqYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('Get') without explaining what 'info' entails (e.g., cluster health, node details, version), whether it's read-only or has side effects, or any rate limits or authentication needs. This leaves critical behavioral traits unspecified.

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 extremely concise at three words, with no wasted language. It's front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness1/5

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

Given the complexity (1 parameter with nested object, no output schema, no annotations), the description is completely inadequate. It doesn't explain what information is returned, how to use the parameter, or behavioral aspects, leaving the agent with insufficient context to use the tool effectively.

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

Parameters1/5

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

The schema has 1 parameter ('req') with 0% description coverage, and the tool description provides no information about parameters. The description doesn't explain what 'req' should contain or how to structure it, failing to compensate for the lack of schema documentation.

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

Purpose3/5

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

The description 'Get Elasticsearch info' clearly states the action (get) and resource (Elasticsearch info), making the basic purpose understandable. However, it's vague about what specific information is retrieved and doesn't distinguish this tool from its sibling 'es-ping' (which likely checks connectivity) or 'es-search' (which searches data).

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, appropriate contexts, or exclusions. With sibling tools like 'es-ping' and 'es-search' available, the agent receives no help in choosing between them.

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