Skip to main content
Glama
code-alchemist01

MCP Cloud Services Server

get_resource_health

Check the health status of cloud resources across AWS, Azure, and GCP to monitor instances, storage, databases, and functions for operational issues.

Instructions

Get health status of a cloud resource

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYesCloud provider
resourceIdYesResource ID
resourceTypeYesResource type

Implementation Reference

  • The handler logic for the 'get_resource_health' tool within the handleMonitoringTool function. It extracts provider, resourceId, and resourceType parameters and returns a placeholder object indicating the health status is unknown as the full implementation is pending.
    case 'get_resource_health': {
      const resourceId = params.resourceId as string;
      const resourceType = params.resourceType as string;
    
      return {
        provider,
        resourceId,
        resourceType,
        health: 'unknown',
        message: 'Resource health check not yet fully implemented',
      };
    }
  • Input schema for the 'get_resource_health' tool, defining required parameters: provider (aws/azure/gcp), resourceId, and resourceType (instance/storage/database/function).
    inputSchema: {
      type: 'object',
      properties: {
        provider: {
          type: 'string',
          enum: ['aws', 'azure', 'gcp'],
          description: 'Cloud provider',
        },
        resourceId: {
          type: 'string',
          description: 'Resource ID',
        },
        resourceType: {
          type: 'string',
          enum: ['instance', 'storage', 'database', 'function'],
          description: 'Resource type',
        },
      },
      required: ['provider', 'resourceId', 'resourceType'],
    },
  • Registration of the 'get_resource_health' tool as part of the exported monitoringTools array, including name, description, and input schema.
      {
        name: 'get_resource_health',
        description: 'Get health status of a cloud resource',
        inputSchema: {
          type: 'object',
          properties: {
            provider: {
              type: 'string',
              enum: ['aws', 'azure', 'gcp'],
              description: 'Cloud provider',
            },
            resourceId: {
              type: 'string',
              description: 'Resource ID',
            },
            resourceType: {
              type: 'string',
              enum: ['instance', 'storage', 'database', 'function'],
              description: 'Resource type',
            },
          },
          required: ['provider', 'resourceId', 'resourceType'],
        },
      },
    ];
  • src/server.ts:74-75 (registration)
    Main server dispatch logic that checks if the tool name matches any in monitoringTools and routes the call to handleMonitoringTool, which implements get_resource_health.
    } else if (monitoringTools.some((t) => t.name === name)) {
      result = await handleMonitoringTool(name, args || {});
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if this is a read-only operation, requires specific permissions, has rate limits, returns real-time vs. cached data, or what the output format looks like. Minimal context is added beyond the basic purpose.

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 with no wasted words. It's front-loaded with the core purpose, making it easy to parse quickly. Every part of the sentence contributes directly 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?

For a tool with 3 required parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'health status' returns (e.g., a status code, detailed report), how to interpret results, or any behavioral constraints. Given the complexity and lack of structured data, more completeness is needed.

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?

Schema description coverage is 100%, so parameters are well-documented in the schema. The description adds no additional meaning about parameters (e.g., how 'resourceId' is formatted or what 'health status' means for different resource types). Baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 action ('Get') and target ('health status of a cloud resource'), making the purpose understandable. It distinguishes from siblings like 'get_resource' (general info) and 'get_metrics' (performance data), but could be more specific about what 'health status' entails (e.g., operational state, availability).

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?

No guidance is provided on when to use this tool versus alternatives like 'get_resource' (general info), 'list_alarms' (alert status), or 'check_compliance' (policy adherence). The description implies usage for health checks but doesn't specify scenarios, prerequisites, or exclusions.

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/code-alchemist01/Cloud-mcp_server'

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