Meilisearch MCP Server

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

Name	Required	Description	Default
`indexUid`	Yes	Unique identifier of the index

Implementation Reference

src/tools/settings-tools.ts:319-328 (handler)
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);
  }
}
```
src/tools/settings-tools.ts:316-318 (schema)
Input schema for the reset-distinct-attribute tool, requiring the indexUid parameter.
```
{
  indexUid: z.string().describe("Unique identifier of the index"),
},
```
src/tools/settings-tools.ts:289-293 (registration)
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",
},
```

src/tools/settings-tools.ts:312-330 (registration)

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);
      }
    }
  );
});

Schema Changelog

Changes observed during successful MCP inspections.

First observedDec 10, 2025

TDQS

C2.9/5.0

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 destructive (likely yes, as it changes settings), rate limits, or what the default value is. The description is minimal and lacks context beyond the basic action.

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 with zero waste. It's appropriately sized and front-loaded, 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 (implied by 'reset'), the description is incomplete. It doesn't explain what the default value is, how the reset affects search behavior, or what the response looks like, leaving significant gaps for an agent to understand the tool's impact.

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 about parameters beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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 it to a 'default value'. It distinguishes from siblings like 'update-distinct-attribute' (which modifies) and 'get-distinct-attribute' (which retrieves), but doesn't explicitly contrast with 'reset-displayed-attributes' or other reset tools beyond the attribute 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 is provided. It doesn't mention prerequisites (e.g., needing an existing index), when not to use it (e.g., if you want to modify rather than reset), or refer to sibling tools like 'update-distinct-attribute' for custom settings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server