Skip to main content
Glama
seohyunjun

OpenSearch MCP Server

by seohyunjun

list_indices

Retrieve a list of all indices in your OpenSearch cluster to manage data organization and monitor storage.

Instructions

List all indices in the Opensearch cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The async handler function that implements the logic for the 'list_indices' MCP tool. It queries the OpenSearch cluster for indices and returns them as TextContent.
    @mcp.tool(description="List all indices in the Opensearch cluster")
    async def list_indices() -> list[TextContent]:
        """
        List all indices in the Opensearch cluster.
        It is important to check the indices before searching documents
        to understand what indices are avilable.
        """
        self.logger.info("Listing indices...")
        try:
            indices = self.es_client.cat.indices(format="json")
            return [TextContent(type="text", text=str(indices))]
        except Exception as e:
            self.logger.error(f"Error listing indices: {e}")
            return [TextContent(type="text", text=f"Error: {str(e)}")]
  • The point where IndexTools.register_tools is called to register the list_indices tool (among others) with the MCP server.
    index_tools.register_tools(self.mcp)
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 states the action but doesn't cover important aspects like whether this is a read-only operation, potential performance impacts, rate limits, or authentication needs. This is a significant gap for a tool that interacts with a cluster.

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 no wasted words. It's front-loaded with the core action and resource, making it highly 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, pagination) or behavioral traits like safety or performance. For a cluster interaction tool, this leaves critical gaps.

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

Parameters4/5

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

The tool has zero parameters, and the schema description coverage is 100% (though empty). The description doesn't need to add parameter details, so it meets the baseline for a parameterless tool. No additional value is required beyond stating the purpose.

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 ('List') and resource ('all indices in the Opensearch cluster'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_index_patterns' or 'get_index_templates', which prevents a perfect 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_index_patterns' or 'get_index_templates'. It lacks context about use cases, prerequisites, or exclusions, leaving the agent with minimal 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/seohyunjun/opensearch-mcp-server'

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