Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

get-synonyms

Retrieve configured synonyms for a Meilisearch index to enhance search relevance by expanding query terms with equivalent words.

Instructions

Get the synonyms setting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexUidYesUnique identifier of the index

Implementation Reference

  • Handler function that performs a GET request to the Meilisearch API for the synonyms settings (/indexes/{indexUid}/settings/synonyms) and returns the JSON-formatted response or an error.
    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 using Zod: requires `indexUid` as a string, the unique identifier of the Meilisearch index.
    {
      indexUid: z.string().describe("Unique identifier of the index"),
    },
  • Configuration object in the `specificSettingsTools` array that specifies the tool name, API endpoint ('synonyms'), and description, used in the dynamic registration loop.
    {
      name: "get-synonyms",
      endpoint: "synonyms",
      description: "Get the synonyms setting",
    },
  • Dynamic registration loop using `server.tool()` for all specific settings tools, including get-synonyms, providing name, description, schema, and shared handler.
    // 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 invocation of `registerSettingsTools(server)` in the main MCP server setup, which registers the get-synonyms 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 the full burden of behavioral disclosure. It implies a read operation ('Get'), but doesn't specify whether this requires permissions, what the output format is, if there are rate limits, or 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 synonyms setting', which is front-loaded and wastes no words. Every part of the sentence contributes to the core purpose, making it efficient in structure.

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 synonyms in a search index context, the description is incomplete. With no annotations, no output schema, and minimal behavioral details, it fails to provide sufficient context for the agent to understand the tool's role, especially compared to sibling tools like 'update-synonyms' or 'reset-synonyms'. It should explain more about what 'synonyms setting' entails and the tool's behavior.

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 schema description coverage is 100%, with the single parameter 'indexUid' fully documented in the schema as 'Unique identifier of the index'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting without compensating for any gaps.

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 synonyms setting' is essentially a tautology that restates the tool name 'get-synonyms' with minimal elaboration. It specifies the verb 'Get' and resource 'synonyms setting', but lacks specificity about what 'synonyms setting' entails (e.g., configuration, list, status) and doesn't distinguish it from sibling tools like 'update-synonyms' or 'reset-synonyms' beyond the basic action.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for usage, or comparisons to sibling tools such as 'update-synonyms', 'reset-synonyms', or 'get-settings', leaving the agent without direction on appropriate scenarios.

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