Skip to main content
Glama

aws_autoscaling_describe_auto_scaling_groups

Retrieve details about AWS Auto Scaling Groups including current capacity, health status, and instance information to monitor and manage scaling resources.

Instructions

List Auto Scaling Groups with their current capacity, health, and instance details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoAWS profile name from ~/.aws/config (e.g., 'default', 'production')
regionNoAWS region override (e.g., 'us-east-1', 'sa-east-1')
auto_scaling_group_namesNoSpecific ASG names (optional — returns all if omitted)
max_recordsNoMaximum ASGs to return
Behavior3/5

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

No annotations provided, so description carries full burden. Verb 'List' implies read-only operation, and specific return fields (capacity, health) disclose what data is retrieved. However, lacks details on pagination behavior, AWS API rate limits, or authentication requirements.

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?

Single sentence with zero waste. Verb-front-loaded construction ('List Auto Scaling Groups...') immediately clarifies action and scope. Every word earns its place.

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?

Despite lacking output schema, description compensates by listing key return value categories (capacity, health, instance details). Complete for a read-only list tool, though could mention AWS API-specific behaviors like pagination tokens.

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 (all 4 parameters documented), establishing baseline score. Description does not discuss parameters, but none are left undocumented given comprehensive schema.

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?

Specific verb 'List' with clear resource 'Auto Scaling Groups' and detailed scope (capacity, health, instance details). Effectively distinguishes from sibling ASG tools like describe_scaling_activities or describe_launch_configurations by specifying exactly what data is returned.

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

Usage Guidelines3/5

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

Provides implied usage through specification of return data (capacity, health, instances), suggesting when to use this versus siblings. However, lacks explicit 'when to use' statements or named alternatives for different ASG operations.

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/marcelobrake/aws-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server