Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-ranking-rules

Retrieve the ranking rules configuration for a Meilisearch index to understand how search results are prioritized and sorted.

Instructions

Get the ranking rules setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function implementing the core logic of the 'get-ranking-rules' tool. It makes an API call to retrieve the ranking-rules settings from Meilisearch for the specified index using the endpoint 'ranking-rules'.
    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 definition for the 'get-ranking-rules' tool, validating the required 'indexUid' parameter using Zod.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object used in the dynamic registration process for the 'get-ranking-rules' tool, specifying its name, API endpoint segment, and description.
    {
      name: "get-ranking-rules",
      endpoint: "ranking-rules",
      description: "Get the ranking rules setting",
    },
  • Dynamic registration loop that registers the 'get-ranking-rules' tool (and other settings getters) on the MCP server using the configuration objects and shared schema/handler template.
    // 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);
          }
        }
      );
    });
  • src/index.ts:67-67 (registration)
    Top-level call to register all settings tools, including 'get-ranking-rules', on the MCP server instance.
    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 the full burden of behavioral disclosure. It states 'Get' implies a read operation, but doesn't specify if it's safe (non-destructive), requires authentication, has rate limits, or what the output format might be. For a tool with zero annotation coverage, this is a significant gap in 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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded with the core action, though it could be slightly more informative without losing conciseness.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what ranking rules are, what the return value looks like (e.g., a list of rules), or behavioral aspects like error handling. For a tool in a complex system with many siblings, more context is needed to guide the agent 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 'Unique identifier of the index'. The description adds no additional meaning beyond this, such as explaining what an index is or how to obtain the identifier. Given the high schema coverage, a baseline score of 3 is appropriate as the schema does the heavy lifting.

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

Purpose3/5

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

The description 'Get the ranking rules setting' clearly states the action (get) and resource (ranking rules setting), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get-settings' or 'get-searchable-attributes' that also retrieve settings, leaving ambiguity about what specifically distinguishes this tool.

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 sibling tools like 'get-settings' (which might include ranking rules) or 'update-ranking-rules' (for modification), nor does it specify prerequisites or contexts for usage, leaving the agent without clear direction.

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