Skip to main content
Glama

ec2-describe_vpcs

Retrieve and filter VPC information for network planning, security auditing, and infrastructure management in AWS environments.

Instructions

Retrieve comprehensive VPC information with advanced filtering for network infrastructure analysis.

This tool provides complete VPC data including CIDR blocks, DNS settings, tenancy, and associated
resources. Essential for network planning, security auditing, and infrastructure management.

**Required Parameters:**
- profile_name (str): AWS profile name from ~/.aws/credentials
- region (str): AWS region (e.g., 'us-east-1', 'eu-west-1')

**Optional Parameters:**
- vpc_ids (List[str]): Specific VPC IDs to retrieve
  Example: ['vpc-12345678', 'vpc-87654321']

- filters (Dict[str, Any]): Advanced filtering options
  **State Filters:**
  - 'state': ['pending', 'available'] - Filter by VPC state

  **Network Configuration:**
  - 'cidr': ['10.0.0.0/16', '172.16.0.0/12'] - Filter by primary CIDR block
  - 'cidr-block-association.cidr-block': ['10.1.0.0/16'] - Filter by any CIDR block
  - 'cidr-block-association.state': ['associated', 'associating', 'disassociated']

  **DNS and Networking:**
  - 'dhcp-options-id': ['dopt-12345678'] - Filter by DHCP options set
  - 'dns-resolution': ['true', 'false'] - Filter by DNS resolution support
  - 'dns-hostnames': ['true', 'false'] - Filter by DNS hostnames support

  **Default VPC:**
  - 'is-default': ['true', 'false'] - Filter default vs custom VPCs

  **Tenancy:**
  - 'instance-tenancy': ['default', 'dedicated', 'host'] - Filter by instance tenancy

  **Ownership:**
  - 'owner-id': ['123456789012'] - Filter by AWS account ID

  **Tag Filters:**
  - 'tag:Name': ['production-vpc', 'staging-vpc'] - Filter by Name tag
  - 'tag:Environment': ['production', 'staging'] - Filter by Environment tag
  - 'tag-key': ['Owner'] - Filter by tag key existence

- max_results (int): Limit results (5-1000). Default: no limit
- next_token (str): Pagination token from previous request

**Common Use Cases:**
1. Find default VPC: filters={'is-default': ['true']}
2. List production VPCs: filters={'tag:Environment': ['production']}
3. Find VPCs with specific CIDR: filters={'cidr': ['10.0.0.0/16']}
4. Audit DNS settings: filters={'dns-resolution': ['true']}
5. Check tenancy: filters={'instance-tenancy': ['dedicated']}

**Response includes:** VPC ID, state, CIDR blocks, DNS resolution settings, DHCP options,
instance tenancy, default VPC flag, owner ID, tags, and associated CIDR block associations.

Critical for network architecture planning and security compliance auditing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYes
profile_nameNodefault
vpc_idsNo
filtersNo
max_resultsNo
next_tokenNo
Behavior4/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 effectively describes what the tool does (retrieves comprehensive VPC data), mentions pagination behavior (next_token parameter), and provides extensive examples of filtering capabilities. It doesn't mention rate limits, authentication requirements beyond parameters, or error conditions, but covers the core behavioral aspects well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections, but it's quite lengthy with extensive filter documentation and use cases. While all content is valuable given the lack of schema descriptions, it could be more front-loaded with the most critical information. Some redundancy exists in the filter explanations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter tool with 0% schema description coverage and no output schema, the description does an excellent job covering parameter semantics and use cases. It describes what the response includes and provides practical examples. The main gap is the lack of explicit error handling or authentication context, but overall it's quite complete for the tool's complexity.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation. It clearly distinguishes required vs optional parameters, provides examples for vpc_ids and filters, explains filter categories with specific key-value pairs, documents default values, and gives practical use cases. This adds substantial meaning beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves comprehensive VPC information with advanced filtering for network infrastructure analysis. It specifies the exact resource (VPCs) and operation (retrieve/describe), distinguishing it from sibling tools like ec2-describe_instances or ec2-describe_security_groups that work with different AWS resources.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context about when to use this tool (network planning, security auditing, infrastructure management) and includes specific common use cases with examples. However, it doesn't explicitly state when NOT to use it or mention alternatives among sibling tools, though the context is sufficiently clear for an AWS EC2 VPC-focused operation.

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/Havoc24k/aws-sa-tools-mcp-server'

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