Skip to main content
Glama

list_internet_gateways

List and view attachments for Internet Gateways in AWS to manage network connectivity and routing configurations.

Instructions

Lists Internet Gateways and their attachments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the list_internet_gateways tool by calling DescribeInternetGatewaysCommand on EC2 client and formatting the response.
    if (name === "list_internet_gateways") {
        const command = new DescribeInternetGatewaysCommand({});
        const response = await ec2Client.send(command);
    
        const igws = response.InternetGateways?.map(igw => ({
            InternetGatewayId: igw.InternetGatewayId,
            Attachments: igw.Attachments,
            Name: igw.Tags?.find(t => t.Key === "Name")?.Value
        })) || [];
    
        return { content: [{ type: "text", text: JSON.stringify(igws, null, 2) }] };
    }
  • src/index.ts:322-329 (registration)
    Registration of the list_internet_gateways tool in the ListTools response, including description and empty input schema.
    {
        name: "list_internet_gateways",
        description: "Lists Internet Gateways and their attachments.",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Input schema for list_internet_gateways tool (empty object).
    inputSchema: {
        type: "object",
        properties: {}
    }
  • Import of DescribeInternetGatewaysCommand used by the tool.
    import { EC2Client, DescribeInstancesCommand, DescribeSecurityGroupsCommand, DescribeAddressesCommand, DescribeVolumesCommand, DescribeVpcsCommand, DescribeSubnetsCommand, DescribeRouteTablesCommand, DescribeInternetGatewaysCommand, DescribeNatGatewaysCommand } from "@aws-sdk/client-ec2";
  • EC2 client instance used by the tool handler.
    const ec2Client = new EC2Client({});
Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does, not how it behaves. It doesn't disclose whether this is a read-only operation, if it requires specific permissions, what format the output takes, or any pagination/rate limiting considerations.

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 directly states the tool's function with zero waste. It's appropriately sized for a simple listing tool and front-loads the essential information.

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 no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned about the gateways and attachments, nor does it provide behavioral context about permissions, scope, or limitations that would help an agent use it correctly.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the empty input. The description appropriately doesn't add parameter information, maintaining focus on the tool's purpose rather than redundant details.

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 ('Lists') and resource ('Internet Gateways and their attachments'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'list_nat_gateways' or 'list_vpcs' beyond naming the specific AWS resource type.

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. The description doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone among many similar 'list_' siblings.

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/bhaveshopss/MCP-server'

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