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

Elasticsearch 7.x MCP Server

by imlewc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

es-ping

Check connectivity and verify the Elasticsearch 7.x server is responsive. Use this tool to test server availability before performing search operations.

Instructions

Ping Elasticsearch server

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

Input Schema

NameRequiredDescriptionDefault
reqYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'ping' without explaining what that entails—whether it's a health check, connectivity test, returns status codes, or has side effects. This leaves significant gaps in understanding the tool's behavior.

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 with just three words, front-loading the essential action and target. There is no wasted language, making it efficient and easy to parse.

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

Completeness2/5

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

Given the complexity of a ping operation (which could involve network checks, authentication, or status returns), no annotations, 0% schema coverage, and no output schema, the description is inadequate. It doesn't provide enough context for an agent to understand how to use the tool effectively or what to expect in return.

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?

The schema description coverage is 0%, and the description provides no information about the single parameter 'req'. It doesn't explain what 'req' should contain, its purpose, or how it affects the ping operation, 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.

Purpose4/5

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

The description clearly states the verb 'ping' and the target resource 'Elasticsearch server', making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'es-info' or 'es-search', but the action is specific enough to understand what it does.

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 like 'es-info' or 'es-search'. The description only states what it does, not when it should be used or what context it applies to.

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