Skip to main content
Glama
code-alchemist01

MCP Cloud Services Server

aws_start_ec2_instance

Start an AWS EC2 instance by providing the instance ID and optional region to launch cloud computing resources.

Instructions

Start an EC2 instance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceIdYesEC2 instance ID
regionNoAWS region

Implementation Reference

  • Core handler implementation: initializes AWS EC2 client with credentials and sends StartInstancesCommand to AWS to start the specified EC2 instance.
    async startEC2Instance(instanceId: string): Promise<void> {
      await this.initializeClients();
      if (!this.ec2Client) throw new Error('EC2 client not initialized');
    
      try {
        const command = new StartInstancesCommand({ InstanceIds: [instanceId] });
        await this.ec2Client.send(command);
      } catch (error) {
        throw new Error(`Failed to start instance: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Tool handler case in handleAWSTool function: extracts instanceId, calls AWSAdapter.startEC2Instance, and returns success message.
    case 'aws_start_ec2_instance': {
      const instanceId = params.instanceId as string;
      await adapter.startEC2Instance(instanceId);
      return { success: true, message: `Instance ${instanceId} started successfully` };
    }
  • Tool registration in awsTools array: defines name, description, and input schema for aws_start_ec2_instance.
    {
      name: 'aws_start_ec2_instance',
      description: 'Start an EC2 instance',
      inputSchema: {
        type: 'object',
        properties: {
          instanceId: {
            type: 'string',
            description: 'EC2 instance ID',
          },
          region: {
            type: 'string',
            description: 'AWS region',
          },
        },
        required: ['instanceId'],
      },
    },
  • Input schema definition for the tool, specifying required instanceId and optional region.
    inputSchema: {
      type: 'object',
      properties: {
        instanceId: {
          type: 'string',
          description: 'EC2 instance ID',
        },
        region: {
          type: 'string',
          description: 'AWS region',
        },
      },
      required: ['instanceId'],
  • src/server.ts:64-66 (registration)
    Top-level tool dispatch in MCP server: routes calls to aws_start_ec2_instance to handleAWSTool.
    if (awsTools.some((t) => t.name === name)) {
      result = await handleAWSTool(name, args || {});
    } else if (azureTools.some((t) => t.name === name)) {
Behavior2/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 states the action ('Start') but doesn't cover critical aspects like required AWS permissions, potential costs, rate limits, or what happens if the instance is already running. This is a significant gap for a mutation tool.

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 zero waste, making it appropriately sized and front-loaded. Every word earns its place by conveying the core action and resource.

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 starting an EC2 instance (a mutation with no annotations and no output schema), the description is incomplete. It lacks details on behavioral traits, error handling, or return values, making it inadequate for safe and effective use by an AI agent.

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 the schema already documents both parameters (instanceId and region). The description doesn't add any meaning beyond what the schema provides, such as format examples or constraints, but the baseline is 3 when schema coverage is high.

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 ('Start') and resource ('an EC2 instance'), providing specific verb+resource pairing. However, it doesn't differentiate from sibling tools like 'start_resource' or 'aws_stop_ec2_instance' beyond the EC2 specificity, which is why it doesn't reach 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 like 'start_resource' or 'aws_stop_ec2_instance', nor does it mention prerequisites such as instance state or permissions. It lacks explicit when/when-not instructions or named alternatives.

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