Skip to main content
Glama
Octodet

octodet-elasticsearch-mcp

get_mappings

Retrieve field mappings for a specified Elasticsearch index to understand its data structure and schema. Input the index name to access detailed mappings.

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

  • Handler function that executes the get_mappings tool: calls esService.getMappings(index), formats success/error response with JSON mappings.
    async ({ index }) => {
      try {
        const mappings = await esService.getMappings(index);
    
        return {
          content: [
            {
              type: "text",
              text: `Mappings for index: ${index}`,
            },
            {
              type: "text",
              text: JSON.stringify(mappings, null, 2),
            },
          ],
        };
      } catch (error) {
        console.error(
          `Failed to get mappings: ${
            error instanceof Error ? error.message : String(error)
          }`
        );
        return {
          content: [
            {
              type: "text",
              text: `Error: ${
                error instanceof Error ? error.message : String(error)
              }`,
            },
          ],
        };
      }
    }
  • Input schema for get_mappings tool: requires 'index' string parameter.
    {
      index: z
        .string()
        .trim()
        .min(1, "Index name is required")
        .describe("Name of the Elasticsearch index to get mappings for"),
    },
  • src/index.ts:144-188 (registration)
    Registration of the get_mappings tool using server.tool(name, description, schema, handler).
    server.tool(
      "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 }) => {
        try {
          const mappings = await esService.getMappings(index);
    
          return {
            content: [
              {
                type: "text",
                text: `Mappings for index: ${index}`,
              },
              {
                type: "text",
                text: JSON.stringify(mappings, null, 2),
              },
            ],
          };
        } catch (error) {
          console.error(
            `Failed to get mappings: ${
              error instanceof Error ? error.message : String(error)
            }`
          );
          return {
            content: [
              {
                type: "text",
                text: `Error: ${
                  error instanceof Error ? error.message : String(error)
                }`,
              },
            ],
          };
        }
      }
    );
  • Helper method in ElasticsearchService that calls the Elasticsearch indices.getMapping API and extracts mappings for the given index.
    async getMappings(index: string): Promise<any> {
      const response = await this.client.indices.getMapping({
        index,
      });
      return response[index]?.mappings || {};
    }
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, implying a read-only operation, but doesn't specify whether it requires specific permissions, returns error details for non-existent indices, or handles pagination/rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 but incomplete. It covers the basic purpose but lacks usage guidelines, behavioral details, and output information, which are needed for effective tool selection and invocation in this context.

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 description mentions 'for a specific Elasticsearch index,' which aligns with the single parameter 'index' in the schema. Since schema description coverage is 100% (the schema fully documents the parameter), the description adds minimal value beyond what's already in the structured data, meeting the baseline for high 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 tool's purpose understandable. However, it doesn't differentiate from siblings like 'get_aliases' or 'get_templates' which also retrieve metadata, so it doesn't fully distinguish itself within the family of Elasticsearch metadata tools.

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. It doesn't mention prerequisites (e.g., index must exist), exclusions, or compare it to siblings like 'list_indices' for broader index information or 'search' for data retrieval, leaving the agent to infer usage context.

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

Related 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/Octodet/elasticsearch-mcp'

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