Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-ranking-rules

Restore default ranking rules for a Meilisearch index to reset search result ordering.

Instructions

Reset the ranking rules setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that executes the reset-ranking-rules tool. It sends a DELETE request to the Meilisearch API at `/indexes/{indexUid}/settings/ranking-rules` (where endpoint='ranking-rules') to reset the ranking rules to default.
        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 validation using Zod for the reset-ranking-rules tool, specifying the required indexUid parameter.
      indexUid: z.string().describe("Unique identifier of the index"),
    },
    async ({ indexUid }) => {
  • Specific configuration object within the resetSettingsTools array that defines the name, endpoint, and description for registering the reset-ranking-rules tool.
    {
      name: "reset-ranking-rules",
      endpoint: "ranking-rules",
      description: "Reset the ranking rules setting to its default value",
    },
  • Registration code block: the forEach loop over resetSettingsTools that calls server.tool() to register each reset tool, including reset-ranking-rules, with its specific 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 states the action ('reset') which implies a mutation, but doesn't disclose behavioral traits such as permissions required, whether it's destructive, rate limits, or what the default value entails. This is a significant gap 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 that front-loads the core action ('reset') and target ('ranking rules setting'), with no wasted words. It's appropriately sized for a simple tool with one parameter and clear purpose.

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 mutation tool, the description is incomplete. It lacks details on behavioral aspects (e.g., safety, response format), usage context, and doesn't compensate for the absence of structured data, making it inadequate for reliable agent invocation.

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' documented in the schema. The description adds no additional meaning beyond what the schema provides, such as explaining the context of 'indexUid' or its format. 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 ('ranking rules setting'), specifying it sets to 'default value'. It distinguishes from siblings like 'update-ranking-rules' by implying a reset vs. update, though not explicitly named. However, it doesn't fully differentiate from other 'reset-*' tools beyond the resource name.

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 explicit guidance on when to use this tool versus alternatives like 'update-ranking-rules' or 'get-ranking-rules' is provided. The description implies usage for resetting to defaults, but lacks context on prerequisites, side effects, or comparisons with sibling tools, leaving the agent to infer from tool names 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