Skip to main content
Glama

list_route_tables

Retrieve AWS VPC route tables with their routes and associations to manage network traffic flow. Filter results by VPC ID for targeted analysis.

Instructions

Lists route tables with their routes and associations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vpc_idNoOptional: Filter by VPC ID.

Implementation Reference

  • Handler function for the 'list_route_tables' tool. Uses AWS EC2 DescribeRouteTablesCommand, optionally filtered by VPC ID, maps response to include routes, associations, and tags.
    if (name === "list_route_tables") {
        const vpcId = (args as any)?.vpc_id;
        const input: any = {};
        if (vpcId) input.Filters = [{ Name: "vpc-id", Values: [vpcId] }];
    
        const command = new DescribeRouteTablesCommand(input);
        const response = await ec2Client.send(command);
    
        const routeTables = response.RouteTables?.map(rt => ({
            RouteTableId: rt.RouteTableId,
            VpcId: rt.VpcId,
            Routes: rt.Routes?.map(r => ({
                DestinationCidrBlock: r.DestinationCidrBlock,
                GatewayId: r.GatewayId,
                NatGatewayId: r.NatGatewayId,
                State: r.State
            })),
            Associations: rt.Associations?.map(a => ({
                RouteTableAssociationId: a.RouteTableAssociationId,
                SubnetId: a.SubnetId,
                Main: a.Main
            })),
            Name: rt.Tags?.find(t => t.Key === "Name")?.Value
        })) || [];
    
        return { content: [{ type: "text", text: JSON.stringify(routeTables, null, 2) }] };
    }
  • src/index.ts:313-321 (registration)
    Registration of the 'list_route_tables' tool in the ListTools response, including name, description, and input schema definition.
        name: "list_route_tables",
        description: "Lists route tables with their routes and associations.",
        inputSchema: {
            type: "object",
            properties: {
                vpc_id: { type: "string", description: "Optional: Filter by VPC ID." }
            }
        }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a list operation, implying read-only behavior, but doesn't mention any constraints like permissions needed, rate limits, pagination behavior, or what happens when no VPC filter is provided. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 communicates the core functionality without unnecessary words. It's appropriately sized for a simple list operation and front-loads the essential information.

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?

For a simple list tool with one optional parameter and no output schema, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more context about what the response contains (beyond mentioning 'routes and associations') and any behavioral constraints. The description meets basic requirements but could be more complete.

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%, with the single parameter 'vpc_id' clearly documented as optional for filtering. The description doesn't add any parameter information beyond what the schema already provides, so the baseline score of 3 is appropriate given the schema does the heavy lifting.

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 verb ('Lists') and resource ('route tables') with additional detail about what information is included ('with their routes and associations'). This is specific and actionable, though it doesn't explicitly differentiate from sibling tools beyond the obvious resource focus.

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 about when to use this tool versus alternatives. While the sibling list includes many other 'list_' tools for different AWS resources, the description doesn't mention any specific context, prerequisites, or exclusions for using this particular tool.

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