Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

create_subscription_request

Create a subscription request to access published data assets in Amazon DataZone. Specify the domain, reason, listings, and principals.

Instructions

Creates a subscription request in Amazon DataZone.

Args: domain_identifier (str): The ID of the domain where the subscription request is created request_reason (str): The reason for the subscription request (1-4096 characters) subscribed_listings (List[Dict[str, str]]): The published assets to subscribe to Example: [{"identifier": "listing-id"}] subscribed_principals (List[Dict[str, Any]]): The principals to subscribe using tagged union format Example for project: [{"project": {"identifier": "project-id"}}] Example for user: [{"user": {"userId": "user-id"}}] metadata_forms (List[Dict[str, str]], optional): Additional metadata forms Example: [{ "content": "form-content", "formName": "form-name", "typeIdentifier": "type-id", "typeRevision": "type-rev" }] client_token (str, optional): A unique token to ensure idempotency

Returns: Any: The API response containing: - Subscription request ID and status - Creation and update timestamps - Domain ID - Request reason and decision comment - Subscribed listings and principals - Metadata forms - Reviewer information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_tokenNo
metadata_formsNo
request_reasonYes
domain_identifierYes
subscribed_listingsYes
subscribed_principalsYes
Behavior3/5

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

No annotations provided, so description must cover behavioral traits. It mentions idempotency via client_token and return values, but lacks disclosure on side effects, permissions, rate limits, or failure modes.

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?

Well-structured with clear purpose, args, and returns sections. Each part adds value, though could be slightly trimmed in parameter examples without losing clarity.

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?

Describes input parameters and return object structure in detail. Lacks error scenarios and prerequisites (e.g., domain existence), but overall sufficient for a create tool with complex parameters.

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?

Description provides detailed explanations and examples for all 6 parameters, including tagged union format for subscribed_principals and length constraints for request_reason, compensating for 0% schema description coverage.

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?

Description clearly states 'Creates a subscription request in Amazon DataZone.' This distinct verb-resource combination differentiates it from siblings like 'accept_subscription_request' and 'get_subscription'.

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?

No explicit guidance on when to use this tool versus alternatives like 'accept_subscription_request'. The description implies it's for creating requests but lacks when-not and precondition information.

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