Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

reset-stop-words

Restores default stop words for a Meilisearch index to improve search relevance by removing common words from filtering.

Instructions

Reset the stop words setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that implements the reset-stop-words tool logic by sending a DELETE request to the Meilisearch API endpoint for stop-words settings.
    async ({ indexUid }) => {
      try {
        const response = await apiClient.delete(`/indexes/${indexUid}/settings/${endpoint}`);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Input schema defining the required 'indexUid' parameter using Zod.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object in the resetSettingsTools array that specifies the name 'reset-stop-words', its endpoint, and description for registration.
    {
      name: "reset-stop-words",
      endpoint: "stop-words",
      description: "Reset the stop words setting to its default value",
    },
  • Registration loop that dynamically registers the 'reset-stop-words' tool (and others) on the MCP server using the configuration from the array, including inline schema and handler.
    resetSettingsTools.forEach(({ name, endpoint, description }) => {
      server.tool(
        name,
        description,
        {
          indexUid: z.string().describe("Unique identifier of the index"),
        },
        async ({ indexUid }) => {
          try {
            const response = await apiClient.delete(`/indexes/${indexUid}/settings/${endpoint}`);
            return {
              content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
            };
          } catch (error) {
            return createErrorResponse(error);
          }
        }
      );
    });
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. It mentions 'reset' which implies a mutation, but doesn't disclose behavioral traits like whether this requires specific permissions, if it's reversible, what happens to existing settings, or any rate limits. The description is minimal and lacks crucial operational context for a mutation tool.

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. It is front-loaded with the core action and target, making it easy to parse quickly. Every word contributes directly to the tool's purpose without redundancy.

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 tool is a mutation (reset) with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like side effects, error conditions, or return values, which are critical for safe and effective use. The minimal description doesn't compensate for the missing structured data.

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 parameter 'indexUid' fully documented in the schema. The description adds no additional meaning about parameters beyond implying the reset applies to a specific index, which is already covered by the schema. Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 ('reset') and the target resource ('stop words setting'), specifying it sets to 'default value'. It distinguishes from sibling tools like 'update-stop-words' by focusing on resetting rather than updating, though it doesn't explicitly mention this distinction. The purpose is specific and actionable.

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 like 'update-stop-words' or 'get-stop-words'. The description lacks context about prerequisites, such as needing an existing index or when resetting is appropriate, leaving the agent to infer usage from the tool 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/devlimelabs/meilisearch-ts-mcp'

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