Skip to main content
Glama
RadiumGu
by RadiumGu

delete_experiment_template

Remove an AWS Fault Injection Service experiment template by specifying its ID to clean up unused chaos engineering configurations and manage resources.

Instructions

Delete an AWS FIS experiment template.

Args:
    template_id: ID of the experiment template to delete
    region: AWS region to use (default: us-east-1)
    
Returns:
    Success or error message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_idYes
regionNous-east-1

Implementation Reference

  • The handler function delete_experiment_template that implements the core logic of the tool. It creates a boto3 FIS client and calls delete_experiment_template(id=template_id). Decorated with @require_write_mode. Returns success message or error.
    def delete_experiment_template(template_id: str, region: str = "us-east-1") -> str:
        """
        Delete an AWS FIS experiment template.
        
        Args:
            template_id: ID of the experiment template to delete
            region: AWS region to use (default: us-east-1)
            
        Returns:
            Success or error message
        """
        try:
            fis = boto3.client('fis', region_name=region)
            fis.delete_experiment_template(id=template_id)
            return f"Successfully deleted experiment template {template_id}"
        except Exception as e:
            return f"Error deleting experiment template: {str(e)}"
  • Registers the delete_experiment_template tool with the FastMCP server using app.tool()(delete_experiment_template).
    app.tool()(delete_experiment_template)
  • The require_write_mode decorator applied to delete_experiment_template and other write operations. It checks if write mode is enabled globally before executing the function.
    def require_write_mode(func):
        """Decorator to require write mode for destructive operations."""
        @wraps(func)
        def wrapper(*args, **kwargs):
            if not _WRITE_MODE_ENABLED:
                return json.dumps({
                    "error": "Write operations are disabled",
                    "message": f"The '{func.__name__}' operation requires write mode. Please restart the server with --allow-writes flag to enable write operations.",
                    "operation": func.__name__,
                    "read_only_mode": True
                }, indent=2)
            return func(*args, **kwargs)
        return wrapper
  • Imports the delete_experiment_template function from aws_fis_mcp.tools module.
        delete_experiment_template,
        list_action_types,
        generate_template_example,
        set_write_mode,
    )
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 states the tool deletes a template, implying a destructive mutation, but lacks details on permissions required, whether deletion is reversible, potential side effects, or rate limits. The return message mention is vague, offering minimal behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the core purpose, followed by parameter and return details. It uses bullet points for clarity, with no redundant sentences. However, the return statement is somewhat vague, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's destructive nature, no annotations, and no output schema, the description is minimally adequate. It covers the basic operation and parameters but lacks critical context like authentication needs, error conditions, or confirmation prompts. For a deletion tool, this leaves significant gaps in safety and usability guidance.

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 description adds meaningful context for both parameters: 'template_id' is explained as 'ID of the experiment template to delete', and 'region' specifies 'AWS region to use (default: us-east-1)'. With 0% schema description coverage, this compensates well by clarifying purpose and defaults, though it could detail format constraints (e.g., ID structure).

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?

The description clearly states the specific action ('Delete') and resource ('AWS FIS experiment template'), making the purpose immediately understandable. It distinguishes this tool from siblings like 'create_experiment_template' or 'get_experiment_template' by specifying the destructive operation.

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. It does not mention prerequisites (e.g., ensuring the template is not in use), exclusions, or compare it to sibling tools like 'list_experiment_templates' for selection. Usage is implied but not explicitly stated.

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/RadiumGu/aws-fis-mcp-server'

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