Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-synonyms

Reset synonyms to default values for a Meilisearch index to restore original 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 implements the core logic of the "reset-synonyms" tool by deleting the synonyms settings endpoint for the given 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);
      }
    }
  • Zod input schema defining the parameters for the reset-synonyms tool (indexUid: string).
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Specific configuration object in resetSettingsTools array used to dynamically register the "reset-synonyms" tool.
    {
      name: "reset-synonyms",
      endpoint: "synonyms",
      description: "Reset the synonyms setting to its default value",
    },
  • The forEach loop that registers all reset tools, including "reset-synonyms", by calling server.tool with the config's name, description, shared 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 full burden. It implies a mutation ('reset'), but doesn't disclose behavioral traits like whether this is destructive (likely yes, as it changes settings), requires specific permissions, has side effects, or returns any output. The description is minimal and lacks operational context.

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 that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, with zero waste.

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 (implied by 'reset') with no annotations and no output schema, the description is incomplete. It lacks details on behavior (e.g., what 'default value' means, whether it's reversible), error conditions, or output format, making it inadequate for safe and effective use by 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' fully documented in the schema. The description adds no parameter-specific information beyond implying the tool applies to an index, which is already clear from the schema. Baseline 3 is appropriate as the schema handles the 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 action ('reset') and the target resource ('synonyms setting'), specifying it sets it to 'its default value'. It distinguishes from sibling tools like 'get-synonyms' (read) and 'update-synonyms' (modify), but doesn't explicitly differentiate from other reset tools (e.g., 'reset-settings').

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), exclusions, or compare with siblings like 'update-synonyms' for custom changes or 'get-synonyms' to check current 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/OrionPotter/iflow-mcp_meilisearch-ts-mcp'

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