Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

get-stop-words

Retrieve configured stop words from a Meilisearch index to understand which common words are excluded from search queries for improved relevance.

Instructions

Get the stop words setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that executes the get-stop-words tool logic: retrieves the stop-words setting from the Meilisearch API for the specified indexUid using the 'stop-words' endpoint.
    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);
      }
    }
  • Zod input schema for the get-stop-words tool, requiring the indexUid parameter.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Registration code that dynamically creates and registers the get-stop-words tool (via the specificSettingsTools array) with the MCP server.
    // 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 registerSettingsTools, which includes registration of the get-stop-words tool.
    registerSettingsTools(server);
  • Configuration object in specificSettingsTools array that specifies the name, endpoint, and description for the get-stop-words tool.
    {
      name: "get-stop-words",
      endpoint: "stop-words",
      description: "Get the stop words setting",
    },
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', implying a read-only operation, but does not clarify if this requires authentication, has rate limits, returns structured data, or involves any side effects. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with a single sentence, 'Get the stop words setting', which is front-loaded and wastes no words. While it may be under-specified, it is not verbose or poorly structured, earning full marks for brevity and clarity within its limited scope.

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 managing stop words in a search index context, the description is incomplete. With no annotations, no output schema, and sibling tools like 'update-stop-words' and 'reset-stop-words', it fails to explain what stop words are, how the setting is returned, or its role in the system. This leaves the agent with insufficient context 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 does not add any meaning beyond this, as it mentions no parameters. 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 stop words setting' is essentially a tautology that restates the tool name 'get-stop-words' with minimal elaboration. While it indicates the action (get) and resource (stop words setting), it lacks specificity about what 'stop words' are in this context or what the 'setting' entails, making it vague compared to more detailed descriptions.

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. Given sibling tools like 'update-stop-words', 'reset-stop-words', and 'get-settings', there is no indication of whether this tool retrieves a subset or full configuration, or any prerequisites. This leaves the agent without context for 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/devlimelabs/meilisearch-ts-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server