Skip to main content
Glama
Brucedh

AWS‑IReveal‑MCP

config_list_discovered_resources

List AWS Config-discovered resources by type and region to identify and manage cloud assets.

Instructions

List resource identifiers that AWS Config has discovered.

Parameters:
  aws_region (str): The AWS region - use 'us-east-1' if not specified.
  resource_type (str): e.g. 'AWS::EC2::Instance'.

Returns:
  JSON list of resourceIdentifier objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aws_regionYes
resource_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'config_list_discovered_resources' tool. It uses AWS Config client to paginate and list discovered resources of a given type in the specified region, returning JSON.
    @mcp.tool()
    async def config_list_discovered_resources(aws_region: str, resource_type: str) -> str:
        """
        List resource identifiers that AWS Config has discovered.
    
        Parameters:
          aws_region (str): The AWS region - use 'us-east-1' if not specified.
          resource_type (str): e.g. 'AWS::EC2::Instance'.
    
        Returns:
          JSON list of resourceIdentifier objects.
        """
        client = boto3.client('config', region_name=aws_region)
        paginator = client.get_paginator('list_discovered_resources')
        all_resources = []
        for page in paginator.paginate(resourceType=resource_type):
            all_resources.extend(page.get('resourceIdentifiers', []))
        return json.dumps(all_resources, indent=2)
  • server.py:703-703 (registration)
    The @mcp.tool() decorator registers this function as an MCP tool.
    @mcp.tool()
Behavior3/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 discloses that the tool lists resources and returns JSON, but lacks details on permissions required, rate limits, pagination behavior, or error conditions. It adds basic behavioral context but misses important operational traits for an AWS API tool.

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 well-structured with clear sections for purpose, parameters, and returns. Each sentence earns its place by providing essential information without redundancy. It is front-loaded with the core purpose and efficiently details parameters and output.

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 2 parameters with 0% schema coverage and an output schema present, the description is largely complete. It explains parameters thoroughly and notes the return format, though it could benefit from more behavioral context like authentication or error handling. The output schema reduces the need to detail return values, making this reasonably complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It fully documents both parameters: 'aws_region' with a default value example and 'resource_type' with an example. This adds significant meaning beyond the bare schema, effectively explaining what each parameter does and how to use them.

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 verb 'List' and the resource 'resource identifiers that AWS Config has discovered', specifying the AWS service context. It distinguishes itself from sibling tools like 'config_describe_compliance_by_resource' or 'config_get_resource_config_history' by focusing on discovered resources rather than compliance or configuration history.

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 when needing to list discovered AWS Config resources, but does not explicitly state when to use this tool versus alternatives like 'config_describe_config_rules' or other AWS Config tools. No exclusions or prerequisites are mentioned, leaving usage context somewhat implied rather than clearly defined.

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