Skip to main content
Glama
Emenowicz

Hybris MCP Server

by Emenowicz

health_check

Verify SAP Commerce Cloud instance availability and operational status to ensure system connectivity and functionality.

Instructions

Check if the Hybris instance is healthy and reachable

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler function that executes the health check logic by attempting a product search to verify Hybris instance connectivity and health.
    async healthCheck(): Promise<{ healthy: boolean; details: Record<string, unknown> }> {
      try {
        // Test connectivity via a simple product search
        const result = await this.searchProducts('', 1, 0);
        return {
          healthy: true,
          details: {
            baseSiteId: this.config.baseSiteId,
            totalProducts: result.pagination?.totalResults ?? 'unknown',
          },
        };
      } catch (error) {
        return {
          healthy: false,
          details: { error: error instanceof Error ? error.message : 'Unknown error' },
        };
      }
    }
  • src/index.ts:323-330 (registration)
    Registration of the 'health_check' tool in the MCP tools list, including name, description, and input schema.
    {
      name: 'health_check',
      description: 'Check if the Hybris instance is healthy and reachable',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the health_check tool (empty object, no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • MCP server handler dispatch for 'health_check' tool, which calls the HybrisClient healthCheck method.
    case 'health_check':
      result = await hybrisClient.healthCheck();
      break;
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 what the tool does (check health/reachability) but doesn't disclose behavioral traits like what 'healthy' means, what metrics are checked, whether it performs active probing or passive checks, timeout behavior, or authentication requirements.

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 front-loads the core purpose without any wasted words. Every word earns its place by specifying the action, target, and what's being assessed.

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 adequate but has gaps. It explains what the tool does but doesn't provide enough context about what constitutes 'healthy' or what the check involves, which would help an agent understand the tool's behavior more completely.

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 with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, focusing instead on the tool's purpose. Baseline is 4 for zero-parameter tools.

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 tool's purpose with a specific verb ('check') and resource ('Hybris instance'), specifying it assesses health and reachability. It distinguishes itself from siblings like get_system_info by focusing specifically on health status rather than general system information.

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 (when you need to verify instance health/connectivity) but doesn't explicitly state when to use this versus alternatives like get_system_info or when not to use it. No explicit alternatives or exclusions are mentioned.

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/Emenowicz/hybris-mcp'

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