Skip to main content
Glama
ckq-aws

Resilience Architect MCP

by ckq-aws

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AWS_ACCESS_KEY_IDYesAWS access key ID for authentication
AWS_SESSION_TOKENNoAWS session token for temporary credentials (optional)
FASTMCP_LOG_LEVELNoLog level for the MCP server (e.g., ERROR, INFO, DEBUG)ERROR
AWS_SECRET_ACCESS_KEYYesAWS secret access key for authentication

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ListFISExperimentsA

Retrieves a list of Experiments available in the AWS FIS service.

This tool fetches all FIS experiments in the current AWS account and region,
organizing them by name for easy reference. It handles pagination automatically.

Returns:
Dict containing experiment details organized by name
GetFISExperimentB

Get detailed information about a specific experiment.

This tool retrieves comprehensive information about a single FIS experiment
identified by its ID.

Args:
    ctx: The MCP context for logging and communication
    id: The experiment ID

Returns:
    Dict containing experiment details
ListFISExperimentTemplatesB

List all experiment templates.

This tool retrieves all FIS experiment templates in the current AWS account and region.
It handles pagination automatically to ensure all templates are returned.

Returns:
    List of experiment templates with their details
GetFISExperimentTemplateC

Get detailed information about a specific experiment template.

This tool retrieves comprehensive information about a single FIS experiment template
identified by its ID.

Args:
    ctx: The MCP context for logging and communication
    id: The experiment template ID

Returns:
    Dict containing experiment template details
StartFISExperimentB

Starts an AWS FIS experiment and returns immediately after starting.

Args:
    ctx: The MCP context for logging and communication
    id: The experiment template ID
    name: Required name for the experiment
    tags: Optional additional tags to apply to the experiment
    action: The actions mode (default: 'run-all')

Returns:
    Dict containing experiment start response

Raises:
    Exception: For AWS API errors or when writes are disabled
CreateFISExperimentTemplateB

Create a new AWS FIS experiment template.

This tool creates a new experiment template that defines the parameters for
fault injection experiments, including targets, actions, and stop conditions.

Args:
    ctx: The MCP context for logging and communication
    clientToken: Client token for idempotency
    description: Description of the experiment template
    role_arn: IAM role ARN for experiment execution
    name: Required name for the experiment template (will be added as Name tag)
    tags: Optional additional tags to apply to the template
    stop_conditions: Conditions that stop the experiment
    targets: Target resources for the experiment
    actions: Actions to perform during the experiment
    log_configuration: Configuration for experiment logging
    experiment_options: Additional experiment options
    report_configuration: Configuration for experiment reporting

Returns:
    Dict containing the created experiment template

Raises:
    Exception: For AWS API errors or when writes are disabled
UpdateFISExperimentTemplateC

Update an existing AWS FIS experiment template.

This tool updates an existing experiment template with new parameters for
fault injection experiments, including targets, actions, and stop conditions.

Args:
    ctx: The MCP context for logging and communication
    id: ID of the experiment template to update
    description: Updated description of the experiment template
    stop_conditions: Updated conditions that stop the experiment
    targets: Updated target resources for the experiment
    actions: Updated actions to perform during the experiment
    role_arn: Updated IAM role ARN for experiment execution
    log_configuration: Updated configuration for experiment logging
    experiment_options: Updated experiment options
    experiment_report_configuration: Updated configuration for experiment reporting

Returns:
    Dict containing the updated experiment template
ListCloudFormationStacksA

Retrieve all AWS CloudFormation Stacks.

This tool lists all CloudFormation stacks in the current AWS account and region,
providing information that can help identify potential targets for fault injection.

Returns:
    Dict containing CloudFormation stack information
GetStackResourcesB

Retrieves the resources that have been created by an individual stack.

This tool lists all resources within a specific CloudFormation stack,
which can be useful for identifying potential targets for fault injection experiments.

Args:
    ctx: The MCP context for logging and communication
    stack_name: Name of the CloudFormation stack

Returns:
    Dict containing stack resources
ListResourceExplorerViewsA

List Resource Explorer views.

This tool retrieves all Resource Explorer views in the current AWS account and region,
which can be used to find and filter resources for fault injection experiments.

Returns:
    List of Resource Explorer views
SearchResourcesB

Search for AWS resources using Resource Explorer.

This tool searches for AWS resources using Resource Explorer based on a query string
and view ARN. It can be used to find specific resources for fault injection experiments.

Args:
    ctx: The MCP context for logging and communication
    query_string: The query string to search for resources
    view_arn: The ARN of the Resource Explorer view to use
    max_results: Maximum number of results to return (default: 100)
    next_token: Token for pagination (optional)

Returns:
    Dict containing search results and pagination information
CreateResourceExplorerViewB

Create a Resource Explorer view.

This tool creates a new Resource Explorer view that can be used to find
and filter resources for fault injection experiments.

Args:
    ctx: The MCP context for logging and communication
    query: Filter string for the view
    view_name: Name of the view
    name: Required name for the view (will be added as Name tag)
    tags: Optional additional tags to apply to the view
    scope: Scope of the view
    client_token: Client token for idempotency

Returns:
    Dict containing the created view details

Raises:
    Exception: For AWS API errors or when writes are disabled
DiscoverResourceRelationshipsA

Discover relationships for a specific AWS resource using AWS Config.

This tool retrieves the configuration history for a specific AWS resource
and returns its relationships with other resources. This is useful for
understanding resource dependencies, such as finding which subnet an ALB
is placed in or which security groups are attached to an instance.

Args:
    ctx: The MCP context for logging and communication
    resource_type: AWS resource type (e.g., AWS::EC2::Instance)
    resource_id: AWS resource ID to discover relationships for
    limit: Maximum number of configuration items to retrieve
    chronological_order: Order of configuration items (Reverse or Forward)

Returns:
    Dict containing resource relationships and configuration details

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 13 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: FIS experiment vs template operations, Resource Explorer view management, resource search vs relationship discovery. The names and descriptions make boundaries clear, and there is no significant overlap that would cause misselection.

Naming Consistency5/5

All tools follow a consistent CamelCase verb-noun pattern (e.g., GetFISExperiment, ListFISExperiments, CreateFISExperimentTemplate). Service prefixes are used consistently within FIS tools, and minor variations like GetStackResources vs ListCloudFormationStacks are justified by different actions.

Tool Count5/5

13 tools is well-scoped for a resilience architecture server covering FIS, Resource Explorer, CloudFormation, and Config. Each tool serves a distinct operation without redundancy, fitting comfortably in the ideal 3-15 range.

Completeness3/5

The surface covers discovery, template creation/update, and experiment start, but lacks critical lifecycle operations like stopping an experiment, deleting templates, and deleting/updating Resource Explorer views. These gaps could hinder full workflow execution for an agent.

Maintenance

ActivityInactive
ResponsivenessNo issues