Skip to main content
Glama

n8n_health_check

Check the health status of your n8n instance to ensure it's running properly and identify any issues affecting workflow execution.

Instructions

Check the health status of the n8n instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the n8n_health_check tool which calls the n8nClient and formats the response.
    case 'n8n_health_check': {
      const isHealthy = await n8nClient.healthCheck();
      return {
        content: [{
          type: 'text',
          text: formatResponse({
            status: isHealthy ? 'healthy' : 'unhealthy',
            url: BASE_URL,
            timestamp: new Date().toISOString(),
          }),
        }],
      };
    }
  • src/index.ts:922-929 (registration)
    The tool registration for n8n_health_check.
    {
      name: 'n8n_health_check',
      description: 'Check the health status of the n8n instance',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The implementation of the health check API call within the N8nClient class.
    async healthCheck(): Promise<boolean> {
      try {
        await this.client.get('/workflows?limit=1');
        return true;
      } catch {
        return false;
      }
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, yet the description fails to disclose what 'health' entails (simple connectivity vs. dependency checks), whether the operation is read-only/safe, potential rate limits, or what response format to expect. It carries the full burden of behavioral disclosure but provides minimal information.

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 single sentence is appropriately front-loaded with the action verb, contains zero redundancy, and is perfectly sized for a zero-parameter diagnostic tool. No extraneous words or formatting issues.

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 (no params, no annotations), the description covers the basic intent but remains insufficient regarding output expectations. Without an output schema or description of return values (e.g., boolean vs. detailed status object), an agent cannot predict what data structure it will receive upon invocation.

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 contains zero parameters, which per the evaluation rules establishes a baseline score of 4. The description correctly implies no configuration is needed for a basic health check.

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 uses a clear verb ('Check') and identifies the resource ('health status of the n8n instance'). It effectively distinguishes itself from the 40+ sibling tools which are all CRUD operations on specific entities (workflows, users, credentials, etc.), though it could specify what aspects of health are validated (API, database, etc.).

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?

Provides no guidance on when to invoke this tool versus other diagnostic options, nor does it indicate prerequisites (e.g., whether it requires authentication unlike public health endpoints) or when to avoid using it. The agent must infer usage context solely from the name.

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/Shravan1610/n8n-mcp-server'

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