Skip to main content
Glama

Second Wind AI

lambda in vpc times out

lambda-vpc-egress-path-trace
Read-onlyIdempotent

Send the function's VPC configuration and the VPC's subnets, route tables, NAT gateways, endpoints and security groups. Traces the call to the internet, an AWS service or a VPC resource from every function subnet separately, so intermittent timeouts caused by one misrouted subnet are identified. Returns each broken hop (public subnet without public address, NAT in the wrong subnet, blackhole route, endpoint without private DNS, group rules) with the command that fixes it. Use when the error reads: Task timed out after seconds in a VPC attached function | connect ETIMEDOUT | Connect timeout on endpoint URL | timeouts on only some invocations. Covers: IPv4 paths inside one VPC from supplied describe output. Network ACLs, DNS, endpoint policies, peering and transit gateway hops beyond the VPC are not evaluated. Price: 4.00 USDC on Base via x402, charged only when the case is solved.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "region": "<region>",
      "function": "<function>",
      "destination": "<destination>",
      "subnets": "<subnets>",
      "route_tables": "<route_tables>",
      "security_groups": "<security_groups>"
    },
    "name": "lambda-vpc-egress-path-trace"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionYes
subnetsYesSubnets from aws ec2 describe-subnets for the function's VPC.
functionYesVpcConfig from aws lambda get-function-configuration.
destinationYes
nat_gatewaysNoNatGateways from aws ec2 describe-nat-gateways.
route_tablesYesRouteTables from aws ec2 describe-route-tables --filters Name=vpc-id,Values=VPC_ID.
vpc_endpointsNoVpcEndpoints from aws ec2 describe-vpc-endpoints --filters Name=vpc-id,Values=VPC_ID.
security_groupsYesSecurityGroups from aws ec2 describe-security-groups for the function groups, endpoint groups and destination groups.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/non-destructive annotations, it discloses what is returned (each broken hop with the fixing command), the per-subnet fan-out that explains intermittent failures, the billing model (4.00 USDC on Base via x402, charged only when solved), and the analysis boundary. This is behavior an agent cannot infer from the annotations.

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?

Dense but front-loaded: the action and per-subnet scope come first, then triggers, then exclusions, then price. Every sentence carries signal, though the error-string list and coverage sentence make it longer than strictly necessary.

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 an 8-parameter nested-object tool with no output schema, it covers purpose, triggers, return shape (broken hop + fix command), analysis boundaries and billing. It stops short of explaining how partial input (e.g., omitted NAT gateways or endpoints) degrades the trace, which an agent juggling 6 required and 2 optional params would want to know.

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 coverage is 75%, so the schema already documents most parameters including AWS describe-command provenance; the description only enumerates which inputs to send ('VPC configuration and the VPC's subnets, route tables, NAT gateways, endpoints and security groups'). It adds no semantics for destination.kind or for what happens when optional inputs (nat_gateways, vpc_endpoints) are omitted.

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?

Names a specific verb and resource ('Traces the call to the internet, an AWS service or a VPC resource from every function subnet separately') and scopes it to egress-path diagnosis, so an agent can distinguish it from sibling tools like security-group-delete-dependency-plan or iam-access-denied-layer-analysis without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit trigger conditions quoting the error text ('Task timed out after <n> seconds...', 'connect ETIMEDOUT', 'Connect timeout on endpoint URL', 'timeouts on only some invocations') and states exclusions clearly: NACLs, DNS, endpoint policies, peering and transit gateway hops are not evaluated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources