Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

update-distinct-attribute

Modify the distinct attribute setting in a Meilisearch index to control how duplicate results are handled during search operations.

Instructions

Update the distinct attribute setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index
valueYesJSON value for the setting

Implementation Reference

  • Configuration object in the updateSettingsTools array that defines the name, endpoint, and description for registering the 'update-distinct-attribute' tool.
    {
      name: "update-distinct-attribute",
      endpoint: "distinct-attribute",
      description: "Update the distinct attribute setting",
    },
  • Shared Zod input schema for all update tools, including 'update-distinct-attribute': requires indexUid (string) and value (stringified JSON).
      indexUid: z.string().describe("Unique identifier of the index"),
      value: z.string().describe("JSON value for the setting"),
    },
  • Handler function shared by update tools: parses the JSON value input, performs a PUT request to the Meilisearch API at `/indexes/${indexUid}/settings/${endpoint}` (where endpoint is 'distinct-attribute' for this tool), and returns the JSON response or handles errors.
      async ({ indexUid, value }) => {
        try {
          // Parse the value string to ensure it's valid JSON
          const parsedValue = JSON.parse(value);
          
          const response = await apiClient.put(`/indexes/${indexUid}/settings/${endpoint}`, parsedValue);
          return {
            content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • The forEach loop that dynamically registers the 'update-distinct-attribute' tool (and other update tools) on the MCP server using server.tool, incorporating the configuration, schema, and handler.
    updateSettingsTools.forEach(({ name, endpoint, description }) => {
      server.tool(
        name,
        description,
        {
          indexUid: z.string().describe("Unique identifier of the index"),
          value: z.string().describe("JSON value for the setting"),
        },
        async ({ indexUid, value }) => {
          try {
            // Parse the value string to ensure it's valid JSON
            const parsedValue = JSON.parse(value);
            
            const response = await apiClient.put(`/indexes/${indexUid}/settings/${endpoint}`, parsedValue);
            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?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update' implies a mutation/write operation, but the description doesn't disclose whether this requires specific permissions, whether changes are immediate or asynchronous, what happens to existing data, or any side effects. For a mutation tool with zero annotation coverage, this represents a significant gap in behavioral transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single sentence with no wasted words. However, this conciseness comes at the cost of being under-specified. While it's front-loaded with the core action, it lacks the necessary detail to be truly helpful for an AI agent trying to understand when and how to use this tool.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'distinct attribute' means in this context, what values are acceptable, what the tool returns, or how it differs from related operations. Given the complexity implied by sibling tools like 'get-distinct-attribute' and 'reset-distinct-attribute', more context is needed to understand this tool's role in the system.

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?

The schema description coverage is 100%, with both parameters ('indexUid' and 'value') having clear descriptions in the schema. The description adds no additional parameter semantics beyond what's already documented in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline score is 3 even with no parameter information in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update the distinct attribute setting' is a tautology that essentially restates the tool name 'update-distinct-attribute'. It doesn't specify what a 'distinct attribute setting' actually does or what resource it affects. While it includes a verb ('Update') and resource ('distinct attribute setting'), it lacks specificity about what this setting controls or its purpose in the system.

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?

The description provides no guidance on when to use this tool versus alternatives. Given the sibling tools include 'get-distinct-attribute' and 'reset-distinct-attribute', there's no indication of when to update versus get or reset. There's no mention of prerequisites, dependencies, or typical use cases for modifying this setting.

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