Skip to main content
Glama

list_auto_scaling_groups

Retrieve AWS Auto Scaling Groups and their capacity configurations to monitor and manage scaling resources.

Instructions

Lists Auto Scaling Groups with their capacity settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for 'list_auto_scaling_groups' tool: sends DescribeAutoScalingGroupsCommand to asgClient, maps response to include group name, sizes, capacity, instance count, and returns JSON.
    if (name === "list_auto_scaling_groups") {
        const command = new DescribeAutoScalingGroupsCommand({});
        const response = await asgClient.send(command);
    
        const asgs = response.AutoScalingGroups?.map(g => ({
            AutoScalingGroupName: g.AutoScalingGroupName,
            MinSize: g.MinSize,
            MaxSize: g.MaxSize,
            DesiredCapacity: g.DesiredCapacity,
            Instances: g.Instances?.length
        })) || [];
    
        return { content: [{ type: "text", text: JSON.stringify(asgs, null, 2) }] };
  • src/index.ts:736-739 (registration)
    Registration of the 'list_auto_scaling_groups' tool in the ListToolsRequestSchema handler, including name, description, and empty input schema.
    {
        name: "list_auto_scaling_groups",
        description: "Lists Auto Scaling Groups with their capacity settings.",
        inputSchema: { "type": "object", "properties": {} }
  • Initialization of the AutoScalingClient (asgClient) used by the tool handler.
    const asgClient = new AutoScalingClient({});
  • Import of AutoScalingClient and DescribeAutoScalingGroupsCommand used in the tool.
    import { AutoScalingClient, DescribeAutoScalingGroupsCommand, DescribeScalingActivitiesCommand } from "@aws-sdk/client-auto-scaling";
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. It mentions the tool lists groups and includes capacity settings, but lacks critical behavioral details: whether it requires specific AWS permissions, if it paginates results, what format the output takes, or any rate limits. For a read operation with zero annotation coverage, this is insufficient.

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 front-loads the core action and resource. Every word contributes meaning without waste, making it easy to parse 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 no annotations and no output schema, the description is incomplete for a tool that likely returns complex data (Auto Scaling Groups with capacity settings). It doesn't explain the return structure, potential errors, or behavioral constraints, leaving significant gaps for the agent to operate effectively.

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 parameters need documentation. The description doesn't add parameter details (as there are none), which is appropriate. Baseline is 4 for zero parameters, as no compensation is needed.

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 ('Auto Scaling Groups') with additional detail about what information is included ('with their capacity settings'). It distinguishes from generic list operations by specifying the resource type, though it doesn't explicitly differentiate from potential similar tools (like 'list_scaling_activities' which is a sibling).

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, prerequisites, or context for selection. It doesn't mention any of the many sibling tools (e.g., 'list_scaling_activities', 'list_ec2_instances') that might be relevant in similar contexts, leaving the agent to infer usage based on name alone.

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