Skip to main content
Glama

list_cloudformation_stacks

Retrieve and display AWS CloudFormation stacks along with their current operational status for monitoring and management purposes.

Instructions

Lists CloudFormation stacks and their status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that lists CloudFormation stacks using ListStacksCommand with specific status filters, maps the response, and returns JSON.
    if (name === "list_cloudformation_stacks") {
        const command = new ListStacksCommand({ StackStatusFilter: ["CREATE_COMPLETE", "UPDATE_COMPLETE", "ROLLBACK_COMPLETE", "CREATE_IN_PROGRESS", "UPDATE_IN_PROGRESS"] });
        const response = await cfnClient.send(command);
        const stacks = response.StackSummaries?.map(s => ({
            StackName: s.StackName,
            StackStatus: s.StackStatus,
            DriftInformation: s.DriftInformation,
            CreationTime: s.CreationTime
        })) || [];
        return { content: [{ type: "text", text: JSON.stringify(stacks, null, 2) }] };
    }
  • src/index.ts:768-771 (registration)
    Tool registration in ListToolsRequestSchema, defining name, description, and empty input schema.
        name: "list_cloudformation_stacks",
        description: "Lists CloudFormation stacks and their status.",
        inputSchema: { "type": "object", "properties": {} }
    },
  • Input schema definition: empty object, no parameters required.
        inputSchema: { "type": "object", "properties": {} }
    },
  • CloudFormationClient instantiation used by the handler.
    const cfnClient = new CloudFormationClient({});
  • Import of CloudFormationClient and ListStacksCommand.
    import { CloudFormationClient, ListStacksCommand } from "@aws-sdk/client-cloudformation";
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions listing stacks and their status, but fails to describe key traits like pagination behavior, authentication requirements, rate limits, or what 'status' entails. This leaves significant gaps for a tool that likely interacts with AWS CloudFormation.

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 without any wasted words. It's appropriately sized for a simple listing tool, making it highly concise and well-structured.

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 complexity of AWS CloudFormation, no annotations, and no output schema, the description is incomplete. It lacks details on output format, error handling, or behavioral context, making it insufficient for an agent to fully understand the tool's operation without additional assumptions.

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 doesn't add parameter details, which is appropriate, earning a baseline score of 4 for adequately handling the lack of 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 ('CloudFormation stacks and their status'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'list_ec2_instances' or 'list_s3_buckets' beyond specifying the AWS service, which is adequate but not exceptional.

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 filtering criteria, prerequisites, or comparisons with other listing tools. It lacks explicit context or exclusions, leaving usage entirely implicit.

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