Skip to main content
Glama
Sign In
AWS MCP Server

AWS MCP Server

by marcelobrake
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aws_vpc_describe_vpc_peering_connections

Retrieve details about VPC peering connections in your AWS account to monitor network configurations and connectivity status.

Instructions

Describe VPC peering connections in the account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "aws_vpc_describe_vpc_peering_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, yet description fails to disclose read-only safety, pagination behavior, or output structure. While "describe" implies read-only in AWS context, explicit confirmation of non-destructive nature is absent.

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

Conciseness4/5

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

Single sentence efficiently conveys core purpose without redundancy. Front-loaded with action verb. Minor deduction for extreme brevity that sacrifices helpful context about limitations.

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

Completeness3/5

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

Minimum viable for a 2-parameter describe operation. Lacks return value documentation given absence of output schema, and omits mention of filtering limitations (underlying AWS API supports filters not exposed in this wrapper).

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?

Input schema has 100% description coverage for both parameters (profile, region). Description adds no parameter-specific context, but baseline 3 is appropriate given comprehensive schema documentation carries the load.

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?

Clear verb ("Describe") and specific resource ("VPC peering connections") with scope ("in the account"). Distinguishes from sibling VPC tools by targeting peering connections specifically. However, lacks scope clarification on whether it returns all connections or supports filtering.

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 provided on when to use this tool versus querying VPCs directly or related networking tools. No mention of prerequisites like IAM permissions or when to specify profile/region overrides.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools