Skip to main content
Glama
NotoriousArnav

EventHorizon MCP Server

health_check

Verify EventHorizon API connectivity and authentication status to ensure reliable platform operations.

Instructions

Check the connection to the EventHorizon API and verify authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the health_check tool: retrieves the API client, performs a health check via API call to verify authentication, and returns a formatted success or error response.
    async () => {
      try {
        const apiClient = getClient();
        const isHealthy = await apiClient.healthCheck();
        if (isHealthy) {
          return {
            content: [{ type: 'text', text: `EventHorizon API is healthy and authenticated.\nConnected to: ${apiClient.getBaseURL()}` }]
          };
        } else {
          return {
            content: [{ type: 'text', text: 'EventHorizon API connection failed.' }],
            isError: true
          };
        }
      } catch (error) {
        return {
          content: [{ type: 'text', text: `Error: ${error instanceof Error ? error.message : String(error)}` }],
          isError: true
        };
      }
    }
  • Empty input schema (no parameters) for the health_check tool.
    {},
  • src/index.ts:392-392 (registration)
    Registers the health_check tool with the MCP server, providing the tool name, description, schema, and handler.
    server.tool(
  • API client method that performs the actual health check by attempting to fetch the current user profile; returns true if successful (authenticated), false otherwise, or throws specific auth error.
    async healthCheck(): Promise<boolean> {
      try {
        await this.client.get('/accounts/api/me/');
        return true;
      } catch (error) {
        if (axios.isAxiosError(error) && error.response?.status === 401) {
          throw new Error('Authentication failed: Invalid or expired Knox token');
        }
        return false;
      }
    }
  • Lazy-initializes and returns the singleton EventHorizonClient instance, validating config first. Used by the health_check handler to get the API client.
    function getClient(): EventHorizonClient {
      if (!client) {
        const errors = validateConfig();
        if (errors.length > 0) {
          throw new Error(`Configuration errors: ${errors.join('; ')}`);
        }
        client = new EventHorizonClient();
      }
      return client;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions checking connection and verifying authentication, which provides some context about what the tool does, but doesn't describe what happens when authentication fails, what specific checks are performed, whether this makes any changes to the system, or what the response format looks like. For a diagnostic tool with zero annotation coverage, this leaves significant behavioral gaps.

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 clearly states the tool's purpose without any wasted words. It's appropriately sized for a simple diagnostic tool and gets straight to the point with no unnecessary elaboration.

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?

For a zero-parameter diagnostic tool with no annotations and no output schema, the description provides the basic purpose but lacks details about what specific checks are performed, what the response contains, or what happens in failure scenarios. While it's complete enough to understand the general function, it doesn't provide sufficient context for an agent to fully understand the tool's behavior and output.

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 zero parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain any parameters, and it doesn't attempt to do so, which is appropriate given the empty input schema.

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 the connection' and 'verify authentication') and the target resource ('EventHorizon API'), distinguishing it from all sibling tools which focus on event management operations rather than system health. It precisely communicates what the tool does without being vague or tautological.

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 context (verifying API connectivity and authentication) but doesn't explicitly state when to use this tool versus alternatives or provide any exclusions. It suggests this is for diagnostic purposes but lacks specific guidance on timing or prerequisites for use.

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/NotoriousArnav/EventHorizon-MCP'

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