Skip to main content
Glama

list_load_balancers

Retrieve all Application and Network Load Balancers from AWS to monitor and manage traffic distribution across your infrastructure.

Instructions

Lists all Application and Network Load Balancers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic of the 'list_load_balancers' tool by calling AWS Elastic Load Balancing v2 DescribeLoadBalancersCommand and formatting the load balancer details for output.
    if (name === "list_load_balancers") {
        const command = new DescribeLoadBalancersCommand({});
        const response = await elbv2Client.send(command);
        const lbs = response.LoadBalancers?.map(lb => ({
            LoadBalancerName: lb.LoadBalancerName,
            DNSName: lb.DNSName,
            Type: lb.Type,
            Scheme: lb.Scheme,
            VpcId: lb.VpcId,
            State: lb.State?.Code,
            LoadBalancerArn: lb.LoadBalancerArn
        })) || [];
        return { content: [{ type: "text", text: JSON.stringify(lbs, null, 2) }] };
    }
  • src/index.ts:558-564 (registration)
    The tool registration entry in the ListToolsRequestSchema handler, which defines the tool's name, description, and input schema (empty object).
        name: "list_load_balancers",
        description: "Lists all Application and Network Load Balancers.",
        inputSchema: {
            type: "object",
            properties: {}
        }
    },
  • Initialization of the ElasticLoadBalancingV2Client used by the list_load_balancers handler.
    const elbv2Client = new ElasticLoadBalancingV2Client({});
  • Import of the AWS SDK client and DescribeLoadBalancersCommand used in the tool implementation.
    import { ElasticLoadBalancingV2Client, DescribeLoadBalancersCommand, DescribeTargetGroupsCommand, DescribeTargetHealthCommand, DescribeListenersCommand, DescribeRulesCommand } from "@aws-sdk/client-elastic-load-balancing-v2";
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Lists') but does not cover critical aspects like pagination, rate limits, authentication needs, output format, or whether it's a read-only operation. This leaves significant gaps in understanding how the tool behaves in practice.

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 purpose without any waste. It is front-loaded and appropriately sized for a simple list operation, making it easy to parse and understand quickly.

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?

Given the tool's complexity (a list operation with no parameters) and lack of annotations and output schema, the description is incomplete. It does not address behavioral traits like output format, pagination, or error handling, which are essential for effective use. This leaves the agent with insufficient context to invoke the tool reliably.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter information, which is appropriate, and it implies no filtering or scoping, aligning with the empty schema. This meets the baseline for tools with no parameters.

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 ('all Application and Network Load Balancers'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'list_target_groups' or 'list_ec2_instances', which might also relate to load balancers in a broader context, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives, such as other list tools for related resources or filtering options. It lacks context on prerequisites, timing, or comparisons to sibling tools, leaving usage unclear beyond the basic purpose.

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