Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

get_environment_blueprint

Retrieve metadata and definition of an environment blueprint in Amazon DataZone, including deployment properties, provisioning configuration, and user parameters.

Instructions

Retrieves metadata and definition of an environment blueprint.

related tools:

  • get_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 in which this blueprint exists. Pattern: ^dzd[-][a-zA-Z0-9-]{1,36}$ identifier (str): The ID of the environment to retrieve. Length Constraints: Minimum length of 0. Maximum length of 128.

Returns: Any: The API response containing the Amazon DataZone blueprint metadata:

    - createdAt (str): Timestamp indicating when the blueprint was created.
    - deploymentProperties (dict): Deployment-related configuration, including:
        - endTimeoutMinutes (int): Timeout in minutes for ending deployment.
        - startTimeoutMinutes (int): Timeout in minutes for starting deployment.
    - description (str): A description of the blueprint.
        - Constraints: 0–2048 characters.
    - glossaryTerms (list of str): Glossary terms associated with the blueprint.
        - Constraints: 1–20 items.
        - Pattern: ^[a-zA-Z0-9_-]{1,36}$
    - id (str): Unique ID of the blueprint.
        - Pattern: ^[a-zA-Z0-9_-]{1,36}$
    - name (str): Name of the blueprint.
        - Constraints: 1–64 characters.
        - Pattern: r"^[\w -]+$"
    - provider (str): The provider of the blueprint.
    - provisioningProperties (dict): Provisioning configuration for the blueprint.
        - Note: This is a union object—only one configuration type may be present.
    - updatedAt (str): Timestamp indicating when the blueprint was last updated.
    - userParameters (list of dict): Custom parameters defined by the user, each including:
        - defaultValue (str): Default value for the parameter.
        - description (str): Description of the parameter.
        - fieldType (str): Type of input field (e.g., string, boolean).
        - isEditable (bool): Whether the parameter is user-editable.
        - isOptional (bool): Whether the parameter is optional.
        - keyName (str): Key name for the parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYes
domain_identifierYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation ('Retrieves') and details the return fields, but does not explicitly state idempotency, permissions, or non-destructive nature. The behavioral traits are partially disclosed but not comprehensively.

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

Conciseness3/5

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

The description is lengthy due to a detailed return schema, but it is well-structured with clear sections for summary, related tools, args, and returns. The front-loading of the main purpose is good, but the verbosity slightly reduces conciseness.

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

Completeness4/5

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

Given the lack of annotations and output schema, the description covers purpose, parameters with constraints, and comprehensive return fields. It also references a related tool. It is complete enough for a read operation, though it omits error conditions or prerequisites.

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 input schema has 0% description coverage, but the description provides meaningful details for both parameters, including patterns and length constraints. This adds significant value beyond the schema, compensating for the lack of schema descriptions.

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 explicitly states 'Retrieves metadata and definition of an environment blueprint,' using a specific verb and resource. It distinguishes from the sibling tool 'get_environment_blueprint_configuration' by noting that the latter retrieves configuration schema, clarifying the purpose.

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 mentions a related tool but provides no explicit guidance on when to use this tool versus alternatives. It lacks statements like 'use this when...' or 'do not use when...', leaving the agent without clear selection criteria.

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