Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-index

Retrieve configuration and metadata for a specific Meilisearch index to manage search functionality and document organization.

Instructions

Get information about a specific Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function for the 'get-index' tool. Fetches specific index information from Meilisearch API using the provided indexUid and returns formatted JSON response or error.
    async ({ indexUid }: GetIndexParams) => {
      try {
        const response = await apiClient.get(`/indexes/${indexUid}`);
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • TypeScript interface defining the input parameters for the get-index tool.
    interface GetIndexParams {
      indexUid: string;
    }
  • Zod schema for input validation of the get-index tool.
      indexUid: z.string().describe('Unique identifier of the index'),
    },
  • Direct registration of the 'get-index' tool within the registerIndexTools function using server.tool().
    server.tool(
      'get-index',
      'Get information about a specific Meilisearch index',
      {
        indexUid: z.string().describe('Unique identifier of the index'),
      },
      async ({ indexUid }: GetIndexParams) => {
        try {
          const response = await apiClient.get(`/indexes/${indexUid}`);
          return {
            content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:64-64 (registration)
    Top-level registration call that invokes registerIndexTools to add index tools, including 'get-index', to the main MCP server instance.
    registerIndexTools(server);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't clarify permissions, rate limits, error conditions, or what specific information is returned (e.g., index settings, statistics, or metadata). For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 a single, clear sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded with the essential action and resource, making it easy to parse quickly. There's zero waste or redundancy in the phrasing.

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, no output schema, and a single parameter with good schema coverage, the description is incomplete. It doesn't explain what information is returned (e.g., index configuration, status, or metadata), which is critical for a 'get' operation. For a tool in a complex ecosystem with many siblings, more context about the return value and usage distinctions is needed.

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?

Schema description coverage is 100%, with the single parameter 'indexUid' clearly documented in the schema. The description doesn't add any meaningful parameter details beyond what the schema provides, such as format examples or constraints. However, with high schema coverage and only one parameter, the baseline score of 3 is appropriate as the schema adequately handles parameter 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 ('Get') and resource ('information about a specific Meilisearch index'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list-indexes' or 'get-document', which would require a more specific scope definition to earn 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-indexes' (for listing all indexes) or 'get-document' (for retrieving documents within an index). There's no mention of prerequisites, context, or comparison with sibling tools, leaving usage decisions ambiguous.

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/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

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