Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-settings

Retrieve all configuration settings for a specific Meilisearch index to manage search behavior and performance parameters.

Instructions

Get all settings for a Meilisearch index

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • The async handler function for the 'get-settings' tool that fetches all settings for the specified Meilisearch index using apiClient.get and returns the JSON-formatted response or an error.
    async ({ indexUid }) => {
      try {
        const response = await apiClient.get(`/indexes/${indexUid}/settings`);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Zod input schema defining the required 'indexUid' parameter as a string.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Registers the 'get-settings' tool on the MCP server with name, description, input schema, and handler function.
    server.tool(
      "get-settings",
      "Get all settings for a Meilisearch index",
      {
        indexUid: z.string().describe("Unique identifier of the index"),
      },
      async ({ indexUid }) => {
        try {
          const response = await apiClient.get(`/indexes/${indexUid}/settings`);
          return {
            content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:67-67 (registration)
    Invokes registerSettingsTools to add the 'get-settings' tool (among others) to the main MCP server instance.
    registerSettingsTools(server);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a read-only operation ('Get'), but doesn't disclose behavioral traits like authentication needs, rate limits, error handling, or what 'all settings' entails (e.g., format, scope). This is a significant gap for a tool with no annotation coverage.

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 with zero waste, front-loading the core purpose. It's appropriately sized for a simple retrieval tool, making it easy to parse quickly.

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 and no output schema, the description is incomplete. It doesn't explain what 'all settings' returns, potential side effects, or error conditions. For a tool with 1 parameter but lacking structured behavioral data, this leaves critical gaps for an agent.

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' well-documented in the schema. The description adds no additional meaning beyond implying the parameter is required, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ('all settings for a Meilisearch index'), making the purpose specific and understandable. It distinguishes from siblings like 'get-index' or 'get-task' by focusing on settings, though it doesn't explicitly contrast with them in the text.

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, when to choose it over other 'get-' tools, or any context-specific usage scenarios, leaving the agent to infer based on the name alone.

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