Skip to main content
Glama
Brucedh

AWS‑IReveal‑MCP

accessanalyzer_get_analyzer

Retrieve detailed information about a specific AWS IAM Access Analyzer by name to review security findings and access policies.

Instructions

Retrieve details of a specific analyzer by name.

Parameters:
    aws_region (str): The AWS region - use 'us-east-1' if not specified.
    analyzer_name (str): The name of the analyzer to retrieve.

Returns:
    str: JSON-formatted details of the analyzer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aws_regionYes
analyzer_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The @mcp.tool()-decorated handler function that implements the 'accessanalyzer_get_analyzer' tool. It fetches and returns JSON details of the specified IAM Access Analyzer using the boto3 accessanalyzer client.
    @mcp.tool()
    async def accessanalyzer_get_analyzer(
        aws_region: str,
        analyzer_name: str
    ) -> str:
        """
        Retrieve details of a specific analyzer by name.
    
        Parameters:
            aws_region (str): The AWS region - use 'us-east-1' if not specified.
            analyzer_name (str): The name of the analyzer to retrieve.
        
        Returns:
            str: JSON-formatted details of the analyzer.
        """
        client = boto3.client('accessanalyzer', region_name=aws_region)
        response = client.get_analyzer(analyzerName=analyzer_name)
        analyzer = response.get('analyzer', {})
        return json.dumps(analyzer, indent=2, cls=DateTimeEncoder)
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 retrieves details (implying a read-only operation) and returns JSON-formatted data, but lacks information on authentication requirements, error handling, rate limits, or whether it's a safe operation. This leaves significant gaps for a tool interacting with AWS services.

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 with the core purpose in the first sentence. The parameter and return sections are structured clearly with bullet points, avoiding redundancy. Every sentence adds value without waste.

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 2 parameters with 0% schema coverage and an output schema (which handles return values), the description is moderately complete. It explains parameter meanings and return format, but as a tool with no annotations and AWS context, it should ideally mention authentication or error behaviors to be fully helpful for an agent.

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 value hint ('use us-east-1 if not specified'), and 'analyzer_name' is 'The name of the analyzer to retrieve'. This compensates well for the schema's lack of descriptions, though it doesn't detail format constraints or examples.

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 'Retrieve' and the resource 'details of a specific analyzer by name', which is specific and unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'accessanalyzer_list_analyzers' (list vs. get specific), though the 'by name' specification implies this distinction.

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 'accessanalyzer_list_analyzers' for listing all analyzers or 'accessanalyzer_get_finding' for different data. It lacks explicit when/when-not instructions or prerequisite context, offering only basic parameter hints.

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