Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

reset-displayed-attributes

Restore default displayed attributes for a Meilisearch index to control which fields appear in search results.

Instructions

Reset the displayed attributes setting to its default value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that executes the reset-displayed-attributes tool logic by sending a DELETE request to the Meilisearch API endpoint for displayed-attributes settings.
    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 for the tool, requiring the indexUid parameter.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object in the resetSettingsTools array that defines the tool's name, endpoint, and description for dynamic registration.
    {
      name: "reset-displayed-attributes",
      endpoint: "displayed-attributes",
      description: "Reset the displayed attributes setting to its default value",
    },
  • src/index.ts:67-67 (registration)
    Top-level call to registerSettingsTools on the MCP server instance, which includes registration of the reset-displayed-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 such as whether this requires specific permissions, if it's destructive (likely yes, as it changes settings), what the default value is, or how it affects existing data. This leaves significant gaps for an agent to understand the tool's impact.

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 any wasted words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (a mutation with one parameter), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic action but lacks details on behavioral context (e.g., effects, permissions) and doesn't explain return values, leaving gaps for an agent to operate effectively.

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 the 'Unique identifier of the index'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the heavy lifting.

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 ('displayed attributes setting'), making the purpose understandable. It distinguishes from siblings like 'get-displayed-attributes' (read) and 'update-displayed-attributes' (modify), but doesn't explicitly mention the sibling 'reset-distinct-attribute' or others, which slightly reduces differentiation.

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. It doesn't mention prerequisites (e.g., needing an existing index), contrast with 'update-displayed-attributes' for custom settings, or reference sibling tools like 'reset-settings' for broader resets, leaving usage context unclear.

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