Skip to main content
Glama
code-alchemist01

MCP Cloud Services Server

get_resource

Retrieve detailed information about cloud resources across AWS, Azure, and GCP by specifying provider, resource ID, and type.

Instructions

Get detailed information about a specific resource

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
providerYesCloud provider
resourceIdYesResource ID
resourceTypeYesResource type

Implementation Reference

  • Handler implementation for the 'get_resource' tool. Extracts resourceId from parameters and returns a placeholder detailed resource information object.
    case 'get_resource': {
      const resourceId = params.resourceId as string;
    
      // Implementation would fetch detailed resource info
      return {
        id: resourceId,
        provider,
        message: 'Detailed resource information retrieval not yet fully implemented',
      };
    }
  • Input schema definition for the 'get_resource' tool, specifying required parameters: provider, resourceId, and resourceType.
    {
      name: 'get_resource',
      description: 'Get detailed information about a specific 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:19-27 (registration)
    Registration of resourceManagementTools (including 'get_resource') into the central allTools array, which is served via ListToolsRequest.
    const allTools = [
      ...awsTools,
      ...azureTools,
      ...gcpTools,
      ...resourceManagementTools,
      ...costAnalysisTools,
      ...monitoringTools,
      ...securityTools,
    ];
  • src/server.ts:70-71 (registration)
    Dispatch/registration logic in MCP server that routes calls to 'get_resource' (and other resourceManagementTools) to the handleResourceManagementTool function.
    } else if (resourceManagementTools.some((t) => t.name === name)) {
      result = await handleResourceManagementTool(name, args || {});
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. While 'Get detailed information' implies a read operation, it doesn't disclose important behavioral aspects like authentication requirements, rate limits, error conditions, or what format the detailed information takes. For a tool with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 gets straight to the point with no wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information about what the tool does.

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 cloud resource management and the lack of both annotations and output schema, the description is insufficient. It doesn't explain what 'detailed information' includes, how results are structured, or any prerequisites for successful invocation. For a tool that presumably returns complex resource metadata, more context 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?

The description adds no parameter-specific information beyond what's already in the schema. Since schema description coverage is 100% with clear descriptions for all three parameters, the baseline score of 3 is appropriate. The description doesn't provide additional context about how these parameters interact or what constitutes a valid resourceId.

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 verb ('Get') and resource ('detailed information about a specific resource'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_resources' or 'get_resource_health', which could cause confusion about when to use this specific retrieval tool versus alternatives.

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 many sibling tools like 'list_resources', 'get_resource_health', and provider-specific listing tools, there's no indication of when this detailed retrieval tool is appropriate versus broader listing or health-checking tools.

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