Skip to main content
Glama
devlimelabs

Meilisearch MCP Server

by devlimelabs

health

Check the operational status of the Meilisearch server to verify its availability and functionality for search operations.

Instructions

Check if the Meilisearch server is healthy

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'health' tool. It sends a GET request to the Meilisearch '/health' endpoint using apiClient and returns the JSON response or an error response.
    async () => {
      try {
        const response = await apiClient.get('/health');
        return {
          content: [{ type: 'text', text: JSON.stringify(response.data, null, 2) }],
        };
      } catch (error) {
        return createErrorResponse(error);
      }
    }
  • Registers the 'health' tool on the MCP server with the given name, description, and empty input schema (no parameters required). The handler is provided inline.
    server.tool(
      'health',
      'Check if the Meilisearch server is healthy',
      {},
  • src/index.ts:69-69 (registration)
    Top-level call to registerSystemTools, which registers the system tools including the 'health' tool.
    registerSystemTools(server);
Behavior3/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 indicates a read-only, non-destructive operation ('Check'), but does not disclose behavioral traits such as response format, error conditions, or whether it performs active probing versus status retrieval. It adds basic context but lacks depth.

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 function without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse and understand immediately.

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 low complexity (0 parameters, no output schema) and lack of annotations, the description is minimally adequate. It covers the basic purpose but does not explain what 'healthy' means in practice (e.g., response indicators, timeouts), leaving gaps for an agent to infer behavior.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, maintaining focus on the tool's purpose without redundancy. Baseline is 4 for zero parameters.

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' by focusing on operational status rather than configuration or performance metrics.

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

Usage Guidelines4/5

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

The description implies usage context—monitoring server health—but does not explicitly state when to use this tool versus alternatives like 'info' (server details) or 'stats' (performance data). It provides clear intent but lacks explicit comparison or exclusion criteria.

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