Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

get_environment_blueprint_configuration

Retrieve the configuration schema and parameters required to provision an environment from an Amazon DataZone blueprint.

Instructions

Gets an Amazon DataZone environment blueprint configuration.

Retrieves the configuration schema and parameters that must be provided when provisioning an environment from a given blueprint.

Args: domain_identifier (str): The ID of the domain where where this blueprint exists. Pattern: ^dzd[-][a-zA-Z0-9-]{1,36}$ identifier (str): The ID of the environment blueprint. Pattern: ^[a-zA-Z0-9_-]{1,36}$

Returns: Any: The API response containing information about the Amazon DataZone environment blueprint configuration:

    - createdAt (str): Timestamp indicating when the blueprint was created.
    - domainId (str): ID of the DataZone domain associated with the blueprint.
        - Pattern: ^dzd[-_][a-zA-Z0-9_-]{1,36}$
    - enabledRegions (list of str): List of AWS regions where the blueprint is enabled.
        - Each region string must follow the pattern: ^[a-z]{2}-?(iso|gov)?-{1}[a-z]*-{1}[0-9]$
        - Length constraints: 4–16 characters.
    - environmentBlueprintId (str): Unique ID of the blueprint.
        - Pattern: ^[a-zA-Z0-9_-]{1,36}$
    - environmentRolePermissionBoundary (str): ARN of the IAM policy that defines the permission boundary for environment roles.
        - Pattern: r"^arn:aws[^:]*:iam::(aws|\d{12}):policy/[\w+=,.@-]*$"
    - manageAccessRoleArn (str): ARN of the IAM role used to manage access to the blueprint.
        - Pattern: ^arn:aws[^:]*:iam::\d{12}:(role|role/service-role)/[\w+=,.@-]*$
    - provisioningConfigurations (list of dict): Provisioning configurations associated with the blueprint.
        - Each item is a `ProvisioningConfiguration` object describing how resources are provisioned.
    - provisioningRoleArn (str): ARN of the IAM role used for provisioning resources.
        - Pattern: ^arn:aws[^:]*:iam::\d{12}:(role|role/service-role)/[\w+=,.@-]*$
    - regionalParameters (dict): A nested map of region-specific parameters.
        - Outer keys: Region codes (e.g., "us-west-2")
            - Constraints: 4–16 characters, pattern: ^[a-z]{2}-?(iso|gov)?-{1}[a-z]*-{1}[0-9]$
        - Inner dicts: Key-value pairs of configuration parameters for that region.
    - updatedAt (str): Timestamp indicating when the blueprint was last updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes
domain_identifierYes
Behavior4/5

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

No annotations provided, so the description carries full burden. It clearly indicates this is a read-only operation (gets configuration) and provides a detailed return structure including fields, patterns, and types. It transparently describes what the tool returns, ensuring the agent knows behavior without hidden side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with clear sections (overall purpose, Args, Returns) and is front-loaded with the main purpose. While somewhat verbose due to detailed patterns and constraints, every part adds value. A minor reduction in length would be possible, but the current structure aids readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the moderate complexity, absence of output schema, and no annotations, the description fully documents the return structure with every field, pattern, and description. The two parameters are thoroughly explained. The tool's behavior and results are completely covered.

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 coverage is 0%, but the description provides complete parameter documentation with patterns and explanations for both 'domain_identifier' and 'identifier'. The Args section adds meaning beyond the schema by explaining the purpose and constraints of each parameter.

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 it gets an Amazon DataZone environment blueprint configuration, specifying the exact resource and action. It distinguishes from sibling tools like 'list_environment_blueprint_configurations' and 'get_environment_blueprint' by focusing on the configuration schema and parameters.

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 does not explicitly state when to use this tool versus alternatives. It implies use for retrieving detailed configuration of a specific blueprint, but lacks guidance on when not to use or alternative tools. Usage context is only suggested by the tool name and general description.

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/awslabs/amazon-datazone-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server