Skip to main content
Glama

check_services_health

Monitor service health status for MCP servers, workers, or infrastructure groups to identify operational issues and ensure system reliability.

Instructions

Check health of one or more services. Safe read-only operation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_groupNoService group: 'all', 'mcp_servers', 'workers', 'infrastructure'
service_namesNoOptional specific service names to check

Implementation Reference

  • Handler for check_services_health tool: destructures arguments, prepares parameters, and calls executeOrchestrator("maintain/health-check", params) to perform the health check.
    case "check_services_health": {
      const { service_group, service_names } = args as {
        service_group?: string;
        service_names?: string[];
      };
      
      const params: Record<string, string> = {};
      
      if (service_group) {
        params.service_group = service_group;
      }
      
      if (service_names) {
        params.service_names = service_names.join(",");
      }
      
      result = executeOrchestrator("maintain/health-check", params);
      break;
    }
  • Input schema definition for the check_services_health tool, specifying service_group and optional service_names.
    {
      name: "check_services_health",
      description: "Check health of one or more services. Safe read-only operation.",
      inputSchema: {
        type: "object",
        properties: {
          service_group: {
            type: "string",
            description: "Service group: 'all', 'mcp_servers', 'workers', 'infrastructure'"
          },
          service_names: {
            type: "array",
            items: { type: "string" },
            description: "Optional specific service names to check"
          }
        }
      }
    },
Behavior3/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 explicitly states 'Safe read-only operation,' which is valuable context about safety and operation type. However, it doesn't describe what 'health' means (e.g., metrics, status codes), whether it requires authentication, rate limits, or what the output looks like (e.g., structured data, alerts).

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 extremely concise with two sentences that earn their place: the first states the purpose, and the second adds critical behavioral context ('Safe read-only operation'). It's front-loaded with the core function and wastes no words.

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 no annotations and no output schema, the description is minimally complete for a read-only health check tool. It covers the basic purpose and safety but lacks details on output format, error handling, or integration with sibling tools. For a tool with 2 parameters and moderate complexity, it should ideally explain what 'health' entails or link to related tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with clear documentation for both parameters ('service_group' with enum-like values and 'service_names' as an optional array). The description adds no additional parameter semantics beyond what's in the schema, such as explaining how parameters interact (e.g., if 'service_names' overrides 'service_group'). Baseline 3 is appropriate given high schema coverage.

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 as 'Check health of one or more services' with the verb 'Check' and resource 'services'. It distinguishes from siblings like 'restart_service' (which modifies) and 'get_infrastructure_status' (which is status-focused rather than health-focused). However, it doesn't explicitly differentiate from 'trigger_auto_recovery' which might also involve health assessment.

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. It doesn't mention when to use 'check_services_health' instead of 'get_infrastructure_status' (which might provide overlapping information) or 'trigger_auto_recovery' (which might be for automated responses to health issues). No context about prerequisites or exclusions is provided.

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/itsablabla/lastrock-mcp'

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