Skip to main content
Glama
Brucedh

AWS‑IReveal‑MCP

config_describe_config_rules

Retrieve details of AWS Config rules to monitor compliance and configuration changes across AWS resources.

Instructions

Describe one or more AWS Config rules, or all rules if none specified.

Parameters:
  aws_region (str): The AWS region - use 'us-east-1' if not specified.
  rule_names (list): optional list of Config rule names.

Returns:
  JSON list of ConfigRule objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aws_regionYes
rule_namesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for 'config_describe_config_rules' tool, registered via @mcp.tool() decorator. Calls AWS Config API to describe rules and returns JSON.
    @mcp.tool()
    async def config_describe_config_rules(
        aws_region: str,
        rule_names: list = None
    ) -> str:
        """
        Describe one or more AWS Config rules, or all rules if none specified.
    
        Parameters:
          aws_region (str): The AWS region - use 'us-east-1' if not specified.
          rule_names (list): optional list of Config rule names.
    
        Returns:
          JSON list of ConfigRule objects.
        """
        client = boto3.client('config', region_name=aws_region)
        if rule_names:
            resp = client.describe_config_rules(ConfigRuleNames=rule_names)
        else:
            resp = client.describe_config_rules()
        rules = resp.get("ConfigRules", [])
        return json.dumps(rules, indent=2, cls=DateTimeEncoder)
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the tool describes AWS Config rules and returns a JSON list, but doesn't disclose behavioral traits such as required permissions, rate limits, pagination, error handling, or whether it's a read-only operation. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 appropriately sized and front-loaded: the first sentence states the core purpose, followed by clear parameter and return sections. Every sentence adds value without redundancy, making it easy to scan and understand quickly.

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 (indicating returns are documented elsewhere) and no annotations, the description is reasonably complete: it covers the purpose, parameters, and return type. However, for a tool with no annotations, it could benefit from more behavioral context (e.g., safety, limitations) to fully guide an agent, though the output schema reduces the need to explain returns.

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 semantics beyond the input schema, which has 0% description coverage. It explains that 'aws_region' is 'The AWS region' with a default of 'us-east-1', and 'rule_names' is an 'optional list of Config rule names'. This clarifies purpose and defaults, compensating well for the schema's lack of descriptions, though it doesn't detail format constraints (e.g., region format).

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 ('AWS Config rules'), specifying it can handle one, multiple, or all rules. However, it doesn't explicitly differentiate from sibling tools like 'config_describe_compliance_by_resource' or 'config_describe_recorder_status', which also describe AWS Config-related entities but focus on different aspects.

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?

The description implies usage by stating it can describe 'one or more AWS Config rules, or all rules if none specified', which provides some context on when to use it (e.g., for listing rules). However, it lacks explicit guidance on when to choose this tool over alternatives like 'config_list_discovered_resources' or other 'describe' tools in the sibling list, and doesn't mention prerequisites or exclusions.

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