Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-sortable-attributes

Reset sortable attributes to default values in a Meilisearch index to restore original search sorting behavior.

Instructions

Reset the sortable attributes setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that performs a DELETE request to reset the 'sortable-attributes' setting for the specified Meilisearch index using the apiClient.
    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 for the tool, requiring an 'indexUid' string parameter.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration entry in the resetSettingsTools array that defines the tool name, endpoint, and description for registration.
    {
      name: "reset-sortable-attributes",
      endpoint: "sortable-attributes",
      description: "Reset the sortable attributes setting to its default value",
    },
  • Registration logic via forEach loop over resetSettingsTools array, calling server.tool for each, including 'reset-sortable-attributes'.
    // Create a reset tool for each specific setting
    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?

With no annotations, the description carries full burden. It states the tool resets to default, implying a mutation, but doesn't disclose behavioral traits such as permissions required, whether it's destructive (likely yes, as it changes settings), rate limits, or what the default value entails. This leaves significant 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 front-loads the core action ('reset') and target. There is no wasted text, making it highly concise and well-structured for quick comprehension.

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 (reset implies change), the description is incomplete. It lacks details on what the default value is, how the reset affects the system, error handling, or response format. For a tool that modifies settings, this leaves too much unspecified.

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 one parameter 'indexUid' clearly documented. The description adds no additional meaning beyond the schema, such as explaining what 'indexUid' represents 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 ('sortable attributes setting'), specifying it's to a default value. It distinguishes from siblings like 'update-sortable-attributes' by implying a reset vs. custom update, though not explicitly named. However, it doesn't fully differentiate from other 'reset-' tools (e.g., 'reset-displayed-attributes'), keeping it at 4.

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 implies usage when reverting to defaults, but lacks context like prerequisites (e.g., after an update) or comparisons to siblings like 'get-sortable-attributes' or 'update-sortable-attributes'. This results in minimal guidance.

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