Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

list_environment_blueprint_configurations

Retrieve a list of environment blueprint configurations in an Amazon DataZone domain, including enabled regions, provisioning roles, and regional parameters.

Instructions

Lists environment blueprints in an Amazon DataZone domain.

Args: domain_identifier (str): The ID of the domain where the blueprint configurations are listed Pattern: ^dzd[-][a-zA-Z0-9-]{1,36}$ max_results (int, optional): Maximum number of blueprint configurations to return (1-50, default: 50) next_token (str, optional): Token for pagination (1-8192 characters)

Returns: dict: A dictionary with the following structure:

Args: items (List[dict]): A list of environment blueprint summaries, each including: - createdAt (str): The timestamp when the blueprint was created. - domainId (str): The identifier of the Amazon DataZone domain. - enabledRegions (List[str]): A list of AWS regions where the blueprint is enabled. - environmentBlueprintId (str): Unique ID of the environment blueprint. - environmentRolePermissionBoundary (str): ARN of the permission boundary used for environment roles. - manageAccessRoleArn (str): ARN of the IAM role used to manage environment access. - provisioningConfigurations (List[dict]): A list of provisioning configuration objects. (Details not expanded here — structure is custom and tool-dependent.) - provisioningRoleArn (str): ARN of the IAM role used to provision environments. - regionalParameters (dict): A dictionary mapping region names to parameter maps. Example: { "us-west-2": { "param1": "value1" } } - updatedAt (str): The timestamp when the blueprint was last updated.

    nextToken (str): Token for paginated results. Use in subsequent requests to retrieve the next set of environment blueprints.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
next_tokenNo
max_resultsNo
domain_identifierYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
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 details return structure and pagination, but does not explicitly state that the operation is read-only or safe. It provides reasonable behavioral context for a list tool but lacks explicit safety disclosure.

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 verbose, with redundant 'Args:' sections and a lengthy return structure. It front-loads the main purpose but could be more concise. The docstring style is structured but includes unnecessary repetition.

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 that an output schema exists (context signal), the description provides comprehensive parameter details and return structure. It covers pagination and parameter constraints. However, it lacks mention of permissions or side effects, which would be helpful for a tool with no annotations.

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?

Schema description coverage is 0%, so the description compensates by explaining each parameter: domain_identifier pattern, max_results range, next_token purpose. It also describes return structure, adding meaning beyond the schema's property names.

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 that the tool 'lists environment blueprints' and specifies the domain context. However, it does not differentiate itself from the sibling tool 'list_environment_blueprints', which could cause confusion. The name includes 'configurations', but the description refers to 'blueprints', slightly ambiguous.

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?

There is no guidance on when to use this tool versus alternatives like 'list_environment_blueprints' or other listing tools. The description only implies usage for listing, without specifying exclusions or prerequisites.

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