Skip to main content
Glama
seohyunjun

OpenSearch MCP Server

by seohyunjun

get_settings

Retrieve configuration settings for a specific OpenSearch index to understand its structure and behavior.

Instructions

Get index settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexYes

Implementation Reference

  • The get_settings tool handler: decorated with @mcp.tool for registration and implements the logic to retrieve OpenSearch index settings using the client, handling errors.
    @mcp.tool(description="Get index settings")
    async def get_settings(index: str) -> list[TextContent]:
        """
        Get the settings for an index.
        
        Args:
            index: Name of the index
        """
        self.logger.info(f"Getting settings for index: {index}")
        try:
            response = self.es_client.indices.get_settings(index=index, h=["index", "health"])
            return [TextContent(type="text", text=str(response))]
        except Exception as e:
            self.logger.error(f"Error getting settings: {e}")
            return [TextContent(type="text", text=f"Error: {str(e)}")]
  • Invocation of register_tools on IndexTools instance, which defines and registers the get_settings tool among others.
    index_tools.register_tools(self.mcp)
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't cover permissions, rate limits, response format, or whether it's read-only or has side effects, which is a significant gap for a tool with no annotation support.

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 a single phrase, front-loaded and zero waste. Every word earns its place, though this brevity contributes to gaps in other dimensions.

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 no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't provide enough context for the agent to understand the tool's behavior, parameters, or output, making it inadequate for a tool with one required parameter.

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?

Schema description coverage is 0%, and the description adds no parameter semantics beyond the schema. It doesn't explain what 'index' means, valid values, or examples, 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 index settings' clearly states the action (get) and resource (index settings), but it's vague about what 'settings' encompasses and doesn't differentiate from siblings like 'get_mapping' or 'get_index_templates' which also retrieve index-related information. It avoids tautology but lacks specificity.

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. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the name alone among similar tools like 'get_mapping' or 'list_indices'.

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/seohyunjun/opensearch-mcp-server'

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