Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

info

Retrieve Meilisearch server system information to monitor performance, check status, and verify configuration for search operations.

Instructions

Get the system information of the Meilisearch server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'info' tool. It makes a GET request to the root endpoint ('/') of the Meilisearch server using apiClient, stringifies the response data as JSON, and returns it in the MCP content format. Errors are handled via createErrorResponse.
    async () => {
      try {
        const response = await apiClient.get('/');
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Registration of the 'info' tool on the MCP server within the registerSystemTools function. It specifies the tool name, description, empty input schema ({}), and the handler function.
    server.tool(
      'info',
      'Get the system information of the Meilisearch server',
      {},
      async () => {
        try {
          const response = await apiClient.get('/');
          return {
            content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • src/index.ts:69-69 (registration)
    Invocation of registerSystemTools on the main MCP server instance, which registers the 'info' tool among other system tools.
    registerSystemTools(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 the tool 'Get[s] the system information' but doesn't specify what information is included (e.g., server configuration, performance metrics, version details), whether it's read-only, or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse for an AI agent.

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 simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate but incomplete. It lacks details on what 'system information' entails and how it differs from sibling tools, which could hinder an agent's ability to use it effectively in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion.

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 verb ('Get') and resource ('system information of the Meilisearch server'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from similar sibling tools like 'health', 'stats', or 'version', which also provide server-related information, so it falls short of a perfect score.

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 when to prefer 'info' over 'health' (server status), 'stats' (index statistics), or 'version' (software version), leaving the agent without context for selection among related tools.

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