Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

reset-synonyms

Reset synonyms to default values for a Meilisearch index to restore standard search behavior and remove custom synonym mappings.

Instructions

Reset the synonyms setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that executes the reset-synonyms tool by sending a DELETE request to the Meilisearch API endpoint `/indexes/{indexUid}/settings/synonyms` to reset synonyms to default values, returning the API response as JSON or an error response.
    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);
      }
    }
  • Zod input schema for the reset-synonyms tool, requiring a string indexUid parameter.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object in resetSettingsTools array that defines the name, endpoint, and description for the reset-synonyms tool.
    {
      name: "reset-synonyms",
      endpoint: "synonyms",
      description: "Reset the synonyms setting to its default value",
    },
  • Dynamic registration loop that calls server.tool() for each reset tool config, including reset-synonyms, using the shared schema and handler template.
    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);
          }
        }
      );
    });
  • src/index.ts:67-67 (registration)
    Invocation of registerSettingsTools on the MCP server instance, which registers the reset-synonyms tool among others.
    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 mutation ('reset'), but doesn't disclose behavioral traits such as required permissions, whether it's reversible, if it triggers background tasks, or what happens to existing custom synonyms. This is inadequate for a mutation tool with zero 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. It is appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., side effects, task handling), usage context, and expected outcomes, which are critical for safe and effective use.

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' fully documented in the schema. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage.

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 ('synonyms setting'), specifying it sets to 'default value'. It distinguishes from sibling 'get-synonyms' (read) and 'update-synonyms' (modify), but doesn't explicitly differentiate from other 'reset-*' tools like 'reset-settings' or 'reset-stop-words'.

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 (e.g., needing an existing index), when not to use it (e.g., if synonyms are already at default), or direct alternatives like 'update-synonyms' for custom values.

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