Skip to main content
Glama
Brucedh

AWS‑IReveal‑MCP

networkinsights_list_scopes

List all Network Access Scopes in your AWS region to analyze and manage network security configurations.

Instructions

Describe all Network Access Scopes in the region.

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

Returns:
    JSON list of NetworkInsightsAccessScope objects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aws_regionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the 'networkinsights_list_scopes' tool. It is registered via the @mcp.tool() decorator and uses the EC2 boto3 client to describe all Network Access Scopes in the specified AWS region, returning the result as a JSON string.
    @mcp.tool()
    async def networkinsights_list_scopes(aws_region: str) -> str:
        """
        Describe all Network Access Scopes in the region.
    
        Parameters:
            aws_region (str): The AWS region - use 'us-east-1' if not specified.
    
        Returns:
            JSON list of NetworkInsightsAccessScope objects.
        """
        client = boto3.client('ec2', region_name=aws_region)
        resp = client.describe_network_insights_access_scopes()
        scopes = resp.get('NetworkInsightsAccessScopes', [])
        return json.dumps(scopes, indent=2, cls=DateTimeEncoder)
  • server.py:813-813 (registration)
    The @mcp.tool() decorator registers the networkinsights_list_scopes function as an MCP tool.
    @mcp.tool()
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 action ('Describe') but lacks details on permissions, rate limits, pagination, or error handling. This is inadequate for a tool that likely interacts 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 well-structured and front-loaded with the core purpose, followed by parameter and return details. Every sentence adds necessary information without redundancy, making it efficient and easy to parse.

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 somewhat complete. However, it lacks behavioral context and usage guidelines, which are important for AWS-related operations, keeping it at an adequate but minimal level.

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?

The description adds value by specifying the parameter 'aws_region' and providing a default value ('use 'us-east-1' if not specified'), which isn't in the input schema (0% coverage). However, it doesn't fully explain the parameter's significance or constraints, keeping it at a baseline level.

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 ('all Network Access Scopes in the region'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'networkinsights_list_analyses' or 'networkinsights_get_findings', 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools, prerequisites, or specific use cases, leaving the agent with minimal context for selection.

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