Skip to main content
Glama

System Health Check

system-health-check

Check system health and database connectivity for Firebird SQL databases to identify issues and ensure reliable operation.

Instructions

Verifica el estado de salud del sistema y la conectividad de la base de datos

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'system-health-check' tool. It collects system health information including status, timestamp, uptime, memory usage, environment details, and tool counts, then formats and returns it.
    handler: async () => {
        try {
            const healthInfo = {
                status: 'healthy',
                timestamp: new Date().toISOString(),
                uptime: process.uptime(),
                memory: {
                    used: Math.round(process.memoryUsage().heapUsed / 1024 / 1024),
                    total: Math.round(process.memoryUsage().heapTotal / 1024 / 1024),
                    external: Math.round(process.memoryUsage().external / 1024 / 1024)
                },
                environment: {
                    nodeVersion: process.version,
                    platform: process.platform,
                    arch: process.arch
                },
                tools: {
                    database: databaseTools.size,
                    metadata: tools.size,
                    total: databaseTools.size + tools.size
                }
            };
    
            return {
                content: [{
                    type: 'text',
                    text: `Estado de salud del sistema:\n\n${formatForClaude(healthInfo)}`
                }]
            };
        } catch (error) {
            logger.error('Error in health check:', { error });
            return {
                content: [{
                    type: 'text',
                    text: `Error en verificación de salud: ${error instanceof Error ? error.message : String(error)}`
                }],
                isError: true
            };
        }
    }
  • Registers the 'system-health-check' tool in the metadata tools Map, defining its title, description, empty input schema, and handler function.
    tools.set('system-health-check', {
        title: 'System Health Check',
        description: 'Verifica el estado de salud del sistema y la conectividad de la base de datos',
        inputSchema: z.object({}),
        handler: async () => {
            try {
                const healthInfo = {
                    status: 'healthy',
                    timestamp: new Date().toISOString(),
                    uptime: process.uptime(),
                    memory: {
                        used: Math.round(process.memoryUsage().heapUsed / 1024 / 1024),
                        total: Math.round(process.memoryUsage().heapTotal / 1024 / 1024),
                        external: Math.round(process.memoryUsage().external / 1024 / 1024)
                    },
                    environment: {
                        nodeVersion: process.version,
                        platform: process.platform,
                        arch: process.arch
                    },
                    tools: {
                        database: databaseTools.size,
                        metadata: tools.size,
                        total: databaseTools.size + tools.size
                    }
                };
    
                return {
                    content: [{
                        type: 'text',
                        text: `Estado de salud del sistema:\n\n${formatForClaude(healthInfo)}`
                    }]
                };
            } catch (error) {
                logger.error('Error in health check:', { error });
                return {
                    content: [{
                        type: 'text',
                        text: `Error en verificación de salud: ${error instanceof Error ? error.message : String(error)}`
                    }],
                    isError: true
                };
            }
        }
    });
  • Defines the input schema for the 'system-health-check' tool as an empty object (no parameters required).
    inputSchema: z.object({}),
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions checking 'estado de salud' (health status) and 'conectividad' (connectivity), which implies a read-only diagnostic operation, but doesn't specify what 'health' entails (e.g., uptime, resource usage, error logs), whether it requires permissions, or what the output format might be. For a tool with zero annotation coverage, this is insufficient detail.

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, concise sentence in Spanish that directly states the tool's purpose without any fluff. It's front-loaded with the core action ('verifica') and resources, making it efficient and easy to parse. Every word contributes to understanding the tool's function.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a system health check tool, the description is incomplete. With no annotations and no output schema, it fails to explain what 'health' means, what metrics or statuses are returned, or how to interpret results. Siblings like 'get-server-info' suggest overlapping functionality, but there's no clarification. For a diagnostic tool, more context is needed to guide effective use.

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 the schema fully documents that no inputs are required. The description doesn't add parameter information, which is appropriate here. Since there are no parameters to explain, a baseline score of 4 is applied, as the description doesn't need to compensate for any gaps.

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: 'Verifica el estado de salud del sistema y la conectividad de la base de datos' (Checks system health status and database connectivity). It specifies the verb 'verifica' (checks) and the resources 'sistema' (system) and 'base de datos' (database). However, it doesn't explicitly differentiate from siblings like 'get-server-info' or 'get-database-info', which might provide overlapping information, so it falls short of a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'get-server-info' and 'get-database-info' that might offer related system or database information, there's no indication of when this health check is preferred or what specific scenarios it addresses. This lack of context leaves the agent to guess based on tool names alone.

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/PuroDelphi/mcpFirebird'

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