Skip to main content
Glama
Brucedh

AWS‑IReveal‑MCP

networkinsights_list_analyses

List and describe network analysis results for AWS access scopes to monitor security configurations and traffic patterns.

Instructions

Describe analyses for one or more scopes.

Parameters:
    aws_region (str): The AWS region - use 'us-east-1' if not specified.
    scope_id (str): The ID of the access scope to filter by.
    analysis_ids (list[str]): List of analysis IDs to filter by.

Returns:
    JSON list of NetworkInsightsAccessScopeAnalysis objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aws_regionYes
scope_idNo
analysis_idsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'networkinsights_list_analyses' MCP tool. It is decorated with @mcp.tool() for registration and implements the logic to list network insights access scope analyses using the AWS EC2 boto3 client, with optional filters by scope_id and analysis_ids.
    @mcp.tool()
    async def networkinsights_list_analyses(
        aws_region: str,
        scope_id: str = None,
        analysis_ids: list[str] = None
    ) -> str:
        """
        Describe analyses for one or more scopes.
    
        Parameters:
            aws_region (str): The AWS region - use 'us-east-1' if not specified.
            scope_id (str): The ID of the access scope to filter by.
            analysis_ids (list[str]): List of analysis IDs to filter by.
    
        Returns:
            JSON list of NetworkInsightsAccessScopeAnalysis objects.
        """
        client = boto3.client('ec2', region_name=aws_region)
        params = {}
        if scope_id:
            params['NetworkInsightsAccessScopeId'] = scope_id
        if analysis_ids:
            params['NetworkInsightsAccessScopeAnalysisIds'] = analysis_ids
        resp = client.describe_network_insights_access_scope_analyses(**params)
        analyses = resp.get('NetworkInsightsAccessScopeAnalyses', [])
        return json.dumps(analyses, 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 mentions the return type ('JSON list of NetworkInsightsAccessScopeAnalysis objects') but fails to cover critical aspects like whether this is a read-only operation, potential rate limits, authentication needs, or pagination behavior. This leaves significant gaps for a tool with three parameters.

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 and understand 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 moderate complexity (3 parameters, no annotations), the description is partially complete. It covers parameters and return values adequately, but lacks behavioral context (e.g., safety, performance). The presence of an output schema helps, but more guidance on usage and limitations is needed for full completeness.

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, which has 0% description coverage. It explains that 'aws_region' defaults to 'us-east-1' if unspecified, clarifies that 'scope_id' and 'analysis_ids' are filters, and specifies their data types. This compensates well for the schema's lack of descriptions.

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 ('analyses for one or more scopes'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'networkinsights_get_findings' or 'networkinsights_list_scopes', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives like 'networkinsights_get_findings' or 'networkinsights_list_scopes'. The description lacks context about use cases, prerequisites, or exclusions, offering only basic parameter information.

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