Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-distinct-attribute

Reset the distinct attribute to its default value in a Meilisearch index to restore standard search behavior.

Instructions

Reset the distinct attribute setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that resets the distinct-attribute setting by sending a DELETE request to the Meilisearch API endpoint `/indexes/${indexUid}/settings/distinct-attribute`. Uses the `endpoint` variable set to 'distinct-attribute' from the tool definition.
    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 for the reset-distinct-attribute tool, requiring the indexUid parameter.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Tool registration entry in the resetSettingsTools array, defining the name, endpoint ('distinct-attribute'), and description. This entry triggers the registration via the subsequent forEach loop.
    {
      name: "reset-distinct-attribute",
      endpoint: "distinct-attribute",
      description: "Reset the distinct attribute setting to its default value",
    },
  • The forEach loop that registers the reset-distinct-attribute tool (and others) by calling server.tool with the name, description, schema, and handler derived from the array entry.
    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 mentions resetting to 'default value' but doesn't disclose behavioral traits such as whether this is a destructive operation, requires specific permissions, has side effects, or how it handles errors. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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. There is zero waste, and it's appropriately sized for a simple tool. Every word earns its place, 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, no output schema, and a mutation tool, the description is incomplete. It lacks details on behavior, side effects, return values, or error handling. While concise, it doesn't provide enough context for safe and effective use, especially compared to siblings with more complex operations.

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 meaning beyond the schema, such as explaining what an index is or how the reset applies. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is provided.

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 ('distinct attribute setting'), specifying it sets to 'default value'. It distinguishes from siblings like 'update-distinct-attribute' by focusing on resetting rather than updating, though it doesn't explicitly name alternatives. 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 explicit guidance on when to use this tool versus alternatives like 'update-distinct-attribute' or 'get-distinct-attribute'. The description implies usage for reverting to defaults but doesn't specify scenarios, prerequisites, or exclusions. This leaves the agent without context for decision-making among similar tools.

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