Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-filterable-attributes

Retrieve the filterable attributes configuration for a Meilisearch index to understand which fields can be used for filtering search results.

Instructions

Get the filterable attributes setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • The handler function that implements the logic for the "get-filterable-attributes" tool. It makes an API call to retrieve the filterable attributes setting from Meilisearch for the given indexUid, using the endpoint "filterable-attributes".
    async ({ indexUid }) => {
      try {
        const response = await apiClient.get(`/indexes/${indexUid}/settings/${endpoint}`);
        return {
          content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Input schema for the "get-filterable-attributes" tool, defining the required indexUid parameter.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object in the specificSettingsTools array used to register the "get-filterable-attributes" tool.
    {
      name: "get-filterable-attributes",
      endpoint: "filterable-attributes",
      description: "Get the filterable attributes setting",
    },
  • The forEach loop that dynamically registers the "get-filterable-attributes" tool (and other specific settings getters) on the MCP server using server.tool.
    // Create a tool for each specific setting
    specificSettingsTools.forEach(({ name, endpoint, description }) => {
      server.tool(
        name,
        description,
        {
          indexUid: z.string().describe("Unique identifier of the index"),
        },
        async ({ indexUid }) => {
          try {
            const response = await apiClient.get(`/indexes/${indexUid}/settings/${endpoint}`);
            return {
              content: [{ type: "text", text: JSON.stringify(response.data, null, 2) }],
            };
          } catch (error) {
            return createErrorResponse(error);
          }
        }
      );
    });
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to do so. It doesn't indicate whether this is a read-only operation, what permissions are required, potential side effects, rate limits, or the format of the returned data. This leaves critical behavioral traits unspecified for a tool that likely interacts with a database or index.

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 with no wasted words, making it highly concise. It's front-loaded with the core action ('Get'), though this brevity contributes to gaps in other dimensions like purpose clarity and guidelines.

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 tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'filterable attributes' are, how they're used, or what the return value includes (e.g., a list of attributes, a configuration object). Given the complexity implied by sibling tools and the lack of structured data, more context is needed for effective use.

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 adds no additional meaning beyond this, such as examples or context for the parameter. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema adequately handles parameter documentation.

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 'Get the filterable attributes setting' restates the tool name with minimal elaboration, making it tautological. While it indicates a retrieval action ('Get'), it doesn't specify what 'filterable attributes' are or how they differ from similar sibling tools like 'get-searchable-attributes' or 'get-sortable-attributes', leaving the purpose vague and undifferentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing index), exclusions, or comparisons to sibling tools like 'get-settings' (which might include filterable attributes) or 'update-filterable-attributes', making it misleadingly incomplete for effective tool selection.

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