Skip to main content
Glama
OrionPotter

Meilisearch MCP Server

by OrionPotter

health

Check if the Meilisearch server is operational and responding to requests to ensure search functionality is available.

Instructions

Check if the Meilisearch server is healthy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration of the 'health' MCP tool, including its description, empty input schema, and inline handler function that queries the Meilisearch /health endpoint.
    server.tool(
      'health',
      'Check if the Meilisearch server is healthy',
      {},
      async () => {
        try {
          const response = await apiClient.get('/health');
          return {
            content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
          };
        } catch (error) {
          return createErrorResponse(error);
        }
      }
    );
  • The core handler logic for the 'health' tool: performs a GET request to '/health', returns formatted JSON response or error.
      async () => {
        try {
          const response = await apiClient.get('/health');
          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 which includes the 'health' tool registration on the main MCP server instance.
    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 full burden. It states the tool checks health but doesn't disclose what 'healthy' means (e.g., response codes, timeouts, error conditions), whether it performs any side effects, or what the output format might be. This leaves significant behavioral gaps for a monitoring tool.

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 that directly states the tool's purpose with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable without any structural fluff.

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 doesn't explain what constitutes 'healthy' or what the agent should expect as a response, which is crucial context for a health-check tool. The lack of output schema means the description should ideally provide more behavioral 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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, and it doesn't need to compensate for any schema gaps. No additional parameter context is required or provided.

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

Purpose5/5

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

The description clearly states the specific action ('Check') and target resource ('Meilisearch server'), with the qualifier 'healthy' precisely defining the purpose. It distinguishes from siblings like 'info', 'stats', or 'version' which provide different status information, making the tool's unique function immediately apparent.

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

Usage Guidelines3/5

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

The description implies usage for server health monitoring but doesn't explicitly state when to use this tool versus alternatives like 'info' (which provides server details) or 'stats' (which provides performance metrics). No guidance on prerequisites, timing, or exclusions is provided, leaving usage context somewhat ambiguous.

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