Skip to main content
Glama
rishab2404

Elasticsearch MCP Server

by rishab2404

get_mappings

Retrieve field mappings for an Elasticsearch index to understand data structure and types.

Instructions

Get field mappings for a specific Elasticsearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYesName of the Elasticsearch index to get mappings for

Implementation Reference

  • The handler function for the get_mappings tool. It fetches the mappings for the specified Elasticsearch index using esClient.indices.getMapping and returns a formatted text response with the mappings or an error message.
    async ({ index }) => {
      console.error("[DEBUG] get_mappings tool called", index);
      try {
        const mappingResponse = await esClient.indices.getMapping({
          index,
        });
    
        return {
          content: [
            {
              type: "text" as const,
              text: `Mappings for index: ${index}`,
            },
            {
              type: "text" as const,
              text: `Mappings for index ${index}: ${JSON.stringify(
                mappingResponse[index]?.mappings || {},
                null,
                2
              )}`,
            },
          ],
        };
      } catch (error) {
        console.error(
          `Failed to get mappings: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
        return {
          content: [
            {
              type: "text" as const,
              text: `Error: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Input schema for the get_mappings tool, which validates that the 'index' parameter is a non-empty trimmed string.
    {
      index: z
        .string()
        .trim()
        .min(1, "Index name is required")
        .describe("Name of the Elasticsearch index to get mappings for"),
    },
  • index.ts:178-228 (registration)
    Registration of the get_mappings tool using server.tool(), including name, description, input schema, and handler function.
      "get_mappings",
      "Get field mappings for a specific Elasticsearch index",
      {
        index: z
          .string()
          .trim()
          .min(1, "Index name is required")
          .describe("Name of the Elasticsearch index to get mappings for"),
      },
      async ({ index }) => {
        console.error("[DEBUG] get_mappings tool called", index);
        try {
          const mappingResponse = await esClient.indices.getMapping({
            index,
          });
    
          return {
            content: [
              {
                type: "text" as const,
                text: `Mappings for index: ${index}`,
              },
              {
                type: "text" as const,
                text: `Mappings for index ${index}: ${JSON.stringify(
                  mappingResponse[index]?.mappings || {},
                  null,
                  2
                )}`,
              },
            ],
          };
        } catch (error) {
          console.error(
            `Failed to get mappings: ${
              error instanceof Error ? error.message : String(error)
            }`
          );
          return {
            content: [
              {
                type: "text" as const,
                text: `Error: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves field mappings but doesn't describe traits like whether it's read-only (implied by 'Get'), error handling for non-existent indices, rate limits, or response format. This leaves significant gaps for a tool with no structured safety hints.

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 a single, clear sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple tool, making it highly efficient.

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?

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, or output, which would be needed for higher completeness in the absence of annotations.

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?

The schema description coverage is 100%, with the single parameter 'index' fully documented in the schema. The description adds no additional meaning beyond what the schema provides (e.g., no extra context about index naming conventions or examples), so it meets the baseline for high schema coverage.

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 action ('Get') and resource ('field mappings for a specific Elasticsearch index'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_indices' or 'search', which might also involve index operations, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list_indices' or 'search'. It lacks context about prerequisites (e.g., index existence) or exclusions, leaving the agent with minimal usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rishab2404/mcp_es'

If you have feedback or need assistance with the MCP directory API, please join our Discord server