Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-filterable-attributes

Restore filterable attributes to default values for a Meilisearch index, clearing custom settings to reset search filtering behavior.

Instructions

Reset the filterable attributes setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that executes the tool by sending a DELETE request to the Meilisearch API endpoint for filterable-attributes settings of the specified 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);
      }
    }
  • Input schema definition using Zod: requires 'indexUid' as a string.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Tool configuration object in the resetSettingsTools array, defining name, endpoint, and description for registration.
    {
      name: "reset-filterable-attributes",
      endpoint: "filterable-attributes",
      description: "Reset the filterable attributes setting to its default value",
    },
  • Registration loop that calls server.tool for each reset tool, including 'reset-filterable-attributes', providing 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);
          }
        }
      );
    });
  • src/index.ts:67-67 (registration)
    Top-level call to registerSettingsTools on the MCP server instance, which includes the reset-filterable-attributes tool.
    registerSettingsTools(server);
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 operation is destructive, requires specific permissions, has side effects (e.g., affecting search results), or involves rate limits. The description is minimal and fails to add meaningful context beyond the basic action, leaving gaps in understanding the tool's behavior.

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 front-loaded with the core action and resource, making it easy to parse quickly. There is zero waste, and every part of the sentence contributes to understanding the tool's function.

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 complexity of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on what 'default value' means, potential impacts on the system, error conditions, or return values. For a tool that modifies settings, this minimal description fails to provide sufficient context 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?

The input schema has 100% description coverage, with 'indexUid' clearly documented as 'Unique identifier of the index'. The description doesn't add any parameter semantics beyond what the schema provides, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract from the existing 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 ('filterable attributes setting'), specifying it sets to 'default value'. It distinguishes from siblings like 'update-filterable-attributes' by focusing on resetting rather than updating, though it doesn't explicitly name alternatives. This provides a specific verb+resource combination that is understandable in context.

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 offers no guidance on when to use this tool versus alternatives like 'update-filterable-attributes' or 'get-filterable-attributes'. It lacks context about prerequisites, such as whether the index must exist or be in a certain state, and doesn't mention any exclusions or conditions for usage. This leaves the agent without clear direction on appropriate scenarios.

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