Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

list_environments

Retrieve a list of Amazon DataZone environments for a specific domain and project, with optional filters like status, name, or profile.

Instructions

Lists environments in Amazon DataZone.

Args: domain_identifier (str): The identifier of the Amazon DataZone domain. project_identifier (str): The identifier of the Amazon DataZone project. max_results (int, optional): Maximum number of environments to return. Defaults to 50. next_token (str, optional): Token for pagination. Defaults to None. aws_account_id (str, optional): The identifier of the AWS account where you want to list environments. aws_account_region (str, optional): The AWS region where you want to list environments. environment_blueprint_identifier (str, optional): The identifier of the Amazon DataZone blueprint. environment_profile_identifier (str, optional): The identifier of the environment profile. name (str, optional): The name of the environment. provider (str, optional): The provider of the environment. status (str, optional): The status of the environments to list. Valid values: ACTIVE, CREATING, UPDATING, DELETING, CREATE_FAILED, UPDATE_FAILED, DELETE_FAILED, VALIDATION_FAILED, SUSPENDED, DISABLED, EXPIRED, DELETED, INACCESSIBLE

Returns: Any: The API response containing environment details or None if an error occurs

Example: >>> list_environments( ... domain_identifier="dzd_4p9n6sw4qt9xgn", ... project_identifier="prj_123456789", ... status="ACTIVE", ... )

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
statusNo
providerNo
next_tokenNo
max_resultsNo
aws_account_idNo
domain_identifierYes
aws_account_regionNo
project_identifierYes
environment_profile_identifierNo
environment_blueprint_identifierNo
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 indicates the tool lists environments (implying read-only) and returns the API response or None on error. It does not explicitly state that it is non-destructive, nor does it disclose prerequisites, permissions, or rate limits. The behavior is partially described but not fully transparent.

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 structured as a clear docstring with Args, Returns, and Example sections. It is front-loaded with the purpose, and every sentence provides necessary information. No redundant or filler content.

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 11 parameters and no output schema, the description documents all parameters and the return type. However, it does not detail the response structure beyond 'API response containing environment details'. Pagination via next_token is mentioned but no further pagination behavior. The example helps, but more response detail would improve completeness.

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?

The input schema has 0% description coverage, but the description includes a full Args block documenting all 11 parameters with brief explanations, types, and defaults. For status, valid enum values are listed. This adds complete meaning beyond the schema, fully 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Lists' and resource 'environments in Amazon DataZone', providing a specific action. However, it does not differentiate from sibling list tools like list_environment_profiles or list_environment_blueprints, relying on the tool name for distinction. This is clear but lacks explicit sibling differentiation, so not a 5.

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. There are many sibling list tools, and the description does not mention when to choose list_environments over list_domains, list_projects, etc. No when-to-use, when-not-to-use, or alternative tool references are given.

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