Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_user_profile

Retrieve user profile details from an Amazon DataZone domain by specifying the domain, user identifier, and profile type.

Instructions

Retrieves the user profile in a specified Amazon DataZone domain for a given user.

Args: domain_identifier (str): The ID of the Amazon DataZone domain from which to retrieve the user profile. Pattern: ^dzd[-][a-zA-Z0-9-]{1,36}$ Required: Yes

type (str): The type of the user profile.
    Valid values: "IAM" | "SSO"
    Required: Yes

user_identifier (str): The identifier of the user for whom to retrieve the profile.
    Pattern: r"(^([0-9a-f]{10}-|)[A-Fa-f0-9]{8}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]{4}-[A-Fa-f0-9]
    {4}-[A-Fa-f0-9]{12}$|^[a-zA-Z_0-9+=,.@-]+$|^arn:aws:iam::\d{12}:.+$)"
    Required: Yes

Returns: dict: A response object containing: - details (dict): A UserProfileDetails object with specific IAM or SSO profile data. - domainId (str): The identifier of the DataZone domain. - id (str): The identifier of the user profile. - status (str): The status of the user profile. Valid values: "ASSIGNED", "NOT_ASSIGNED", "ACTIVATED", "DEACTIVATED". - type (str): The type of the user profile. Valid values: "IAM", "SSO".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_typeNo
user_identifierYes
domain_identifierYes

Tool Definition Quality

B3.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It indicates a read operation (retrieve) and details return structure, but lacks information on required permissions, side effects, or error conditions. The return format is well-described.

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?

Description is moderately concise with structured Args/Returns sections. However, it repeats info that could be in schema annotations (patterns, valid values) and includes a line break in the pattern string. Some redundancy.

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 no output schema and no annotations, the description adequately explains input parameters and return values. However, it lacks prerequisites, error handling, and does not address the mismatch with the input schema. Incomplete for a tool with 3 parameters and no other structured context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. The description adds patterns and valid values for parameters, but there is a contradiction: description names parameter 'type' with required status, while schema has 'user_type' not required. This mismatch reduces reliability and could confuse agents.

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 the tool retrieves a user profile in a specified Amazon DataZone domain for a given user. The verb 'retrieves' and resource 'user profile' are specific. Among siblings like search_user_profiles, this tool uniquely identifies a single profile by identifiers.

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?

No explicit guidance on when to use this tool vs alternatives. With 47 sibling tools including search_user_profiles, the description does not clarify when to use a direct retrieval versus a search. Implied usage only.

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