Skip to main content
Glama
victor-velazquez-ai

Enterprise MCP Template

health

Check server status, verify configuration, and retrieve version information to monitor system health and ensure operational readiness.

Instructions

Health check for the MCP server. Returns server status, configuration validity, and version information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'health' MCP tool is registered with @mcp.tool() and implemented as the 'health' function, which returns diagnostic information about the server status and configuration.
    @mcp.tool()
    def health() -> Dict[str, Any]:
        """
        Health check for the MCP server.
        Returns server status, configuration validity, and version information.
        """
        config = get_config()
        oauth_ready = _auth_provider is not None
        account_preconfigured = bool(config.upstream.build_api_base_url())
    
        return {
            "status": HealthStatus.HEALTHY.value,
            "server": config.server.server_name,
            "version": __version__,
            "timestamp": datetime.now(timezone.utc).isoformat(),
            "oauth_enabled": oauth_ready,
            "api_preconfigured": account_preconfigured,
            "authentication_mode": "oauth" if oauth_ready else ("preconfigured" if account_preconfigured else "not_configured"),
            "ready_for_use": oauth_ready or account_preconfigured,
        }
Behavior4/5

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

No annotations provided, so description carries full burden. It successfully discloses return payload contents (server status, configuration validity, version information). Could improve by explicitly stating it's read-only/safe, but adequately covers the key behavioral trait for a health endpoint.

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?

Two sentences with zero waste. First establishes purpose, second details return values. Perfectly front-loaded and appropriately sized for tool complexity.

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

Completeness4/5

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

Given 0 parameters and existence of output schema (per context signals), description provides sufficient context by disclosing the nature of returned information. Complete for a simple health-check tool, though mentioning read-only nature would provide full coverage.

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?

Zero parameters present. Per rubric, 0 params = baseline 4. The description correctly avoids inventing parameter semantics where none exist.

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?

Specific verb ('Health check') + resource ('MCP server') clearly stated. The return value details (status, configuration validity, version) effectively distinguish it from sibling 'ping' (likely a simple connectivity check), establishing a distinct purpose.

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?

No explicit 'when to use' or comparison to sibling alternatives provided. While 'health check' is self-explanatory, the description doesn't state prerequisites or when to prefer this over 'ping' for connectivity checks.

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/victor-velazquez-ai/enterprise-mcp-template'

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