Skip to main content
Glama
Brucedh

AWS‑IReveal‑MCP

guardduty_list_detectors

Retrieve all GuardDuty detector IDs from a specified AWS region to monitor security threats and manage detection configurations.

Instructions

List all GuardDuty detector IDs in the specified AWS region.

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

Returns:
  str: JSON-formatted list of detector IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aws_regionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'guardduty_list_detectors' tool. It uses the AWS GuardDuty boto3 client to list detector IDs in the specified region and returns them as JSON or an error message.
    @mcp.tool()
    async def guardduty_list_detectors(aws_region: str) -> str:
        """
        List all GuardDuty detector IDs in the specified AWS region.
    
        Parameters:
          aws_region (str): The AWS region - use 'us-east-1' if not specified.
    
        Returns:
          str: JSON-formatted list of detector IDs.
        """
        try:
            client = boto3.client('guardduty', region_name=aws_region)
            response = client.list_detectors()
            detectors = response.get("DetectorIds", [])
            return json.dumps(detectors, indent=2)
        except Exception as e:
            return f"Error listing GuardDuty detectors: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it lists IDs and returns JSON. It lacks critical behavioral details such as whether this is a read-only operation, if it requires specific permissions, rate limits, pagination behavior, or error handling for invalid regions.

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 a clear purpose statement followed by parameter and return sections. Every sentence adds value without redundancy, making it easy to parse quickly.

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 low complexity (1 parameter) and the presence of an output schema (which covers return values), the description is minimally adequate. However, it lacks behavioral context and usage guidelines, which are important for an AWS tool with siblings.

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

Parameters3/5

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

Schema description coverage is 0%, but the description adds meaningful context by specifying the parameter's purpose and a default value ('us-east-1'). This partially compensates for the schema gap, though it doesn't detail format constraints or validation rules.

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 ('List') and resource ('all GuardDuty detector IDs'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'guardduty_list_findings' or other list operations, which would require a 5.

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 like 'guardduty_get_findings' or other AWS listing tools. It mentions a default region but offers no context about prerequisites, dependencies, or typical use cases.

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