Skip to main content
Glama
Brucedh

AWS‑IReveal‑MCP

config_describe_recorder_status

Check AWS Config recorder status to monitor configuration compliance and track changes across AWS resources in a specified region.

Instructions

Describe status of AWS Config recorder(s).

Parameters:
  aws_region (str): The AWS region - use 'us-east-1' if not specified.

Returns:
  JSON list of ConfigurationRecorderStatus objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aws_regionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'config_describe_recorder_status' tool. It uses boto3 to call describe_configuration_recorder_status in AWS Config service and returns the JSON serialized recorder statuses. The @mcp.tool() decorator registers it as an MCP tool, and the docstring provides schema information via parameters and return description.
    @mcp.tool()
    async def config_describe_recorder_status(aws_region: str) -> str:
        """
        Describe status of AWS Config recorder(s).
        
        Parameters:
          aws_region (str): The AWS region - use 'us-east-1' if not specified.
    
        Returns:
          JSON list of ConfigurationRecorderStatus objects.
        """
        client = boto3.client('config', region_name=aws_region)
        resp = client.describe_configuration_recorder_status()
        statuses = resp.get("ConfigurationRecorderStatuses", [])
        return json.dumps(statuses, indent=2, cls=DateTimeEncoder)
  • server.py:687-687 (registration)
    The @mcp.tool() decorator registers the config_describe_recorder_status function as an MCP tool.
    @mcp.tool()
  • Docstring defining the input parameter 'aws_region' and output as JSON list of ConfigurationRecorderStatus objects, serving as the tool schema.
    """
    Describe status of AWS Config recorder(s).
    
    Parameters:
      aws_region (str): The AWS region - use 'us-east-1' if not specified.
    
    Returns:
      JSON list of ConfigurationRecorderStatus objects.
    """
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't mention authentication requirements, rate limits, error conditions, whether it's read-only or has side effects, or any performance characteristics. The description is functional but lacks important operational context.

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 efficiently structured with clear sections: purpose statement, parameters with explanation, and return value specification. Every sentence earns its place, and the information is front-loaded with the core purpose first. No wasted words or redundancy.

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?

Given the tool has an output schema (returns JSON list of ConfigurationRecorderStatus objects), the description doesn't need to detail return values. For a single-parameter read operation with output schema, the description covers the essentials: what it does, the parameter meaning, and return type. The main gap is lack of behavioral context that annotations would normally provide.

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 beyond the schema. While the schema only shows 'aws_region' as a required string parameter, the description specifies it's for AWS region selection and provides a default value suggestion ('use "us-east-1" if not specified'). This compensates well for the 0% schema description coverage with a single parameter.

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 ('describe') and resource ('status of AWS Config recorder(s)'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'config_describe_compliance_by_resource' or 'config_describe_config_rules' beyond the specific resource type.

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. There's no mention of prerequisites, when this operation is appropriate, or how it differs from other config_* tools in the sibling list. The only contextual hint is the default region suggestion in the parameter section.

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

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