Skip to main content
Glama
awslabs

amazon-datazone-mcp-server

Official
by awslabs

search_types

Search for type definitions in Amazon DataZone by specifying domain, scope, and criteria. Returns matching asset, form, or lineage node types.

Instructions

Invokes the SearchTypes action in a specified Amazon DataZone domain to retrieve type definitions (e.g., asset types, form types, or lineage node types) that match the search criteria.

Args: domain_identifier (str): The identifier of the Amazon DataZone domain in which to invoke the SearchTypes action. Pattern: ^dzd[-][a-zA-Z0-9-]{1,36}$ (Required)

managed (bool): Whether the search is for managed types. (Required)

filters (dict, optional): A FilterClause object specifying a single filter for the search.
    Only one member of the union type may be used.

max_results (int, optional): The maximum number of results to return in a single call.
    Valid range: 1–50. Default is service-defined.

next_token (str, optional): Token for paginating results. Used to retrieve the next page of results
    when the number of results exceeds max_results.
    Length constraints: 1–8192 characters.

search_in (List[dict], optional): A list of SearchInItem objects specifying search fields.
    Minimum of 1 item, maximum of 10.

search_scope (str): The scope of the search. Valid values:
    "ASSET_TYPE", "FORM_TYPE", "LINEAGE_NODE_TYPE". (Required)

search_text (str, optional): The free-text string to search for.
    Length constraints: 1–4096 characters.

sort (dict, optional): A SearchSort object specifying how to sort the results.

Returns: dict: A response object containing: - items (List[dict]): A list of SearchTypesResultItem objects matching the query. - nextToken (str): A pagination token for retrieving the next set of results. - totalMatchCount (int): Total number of matching items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo
filtersNo
managedYes
search_inNo
next_tokenNo
max_resultsNo
search_textNo
search_scopeYes
domain_identifierYes
owning_project_identifierNo
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention whether the operation is read-only, requires specific permissions, has rate limits, or any side effects. For a search action, it likely is read-only, but this is not stated, leaving a gap in transparency.

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?

The description is structured as a clear docstring with Args and Returns sections. It is front-loaded with the main purpose. However, it is somewhat lengthy due to detailed parameter descriptions; a more concise summary could be beneficial, but overall it remains well-organized and readable.

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 10 parameters, no output schema, and no annotations, the description covers all parameters and return values comprehensively, including pagination and defaults. The only missing element is behavioral transparency (e.g., idempotency, permissions), but for a search tool, the parameter and return coverage is sufficient for an agent to invoke it correctly.

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?

With 0% schema description coverage, the description compensates fully. It provides detailed explanations for each parameter, including regex patterns, valid ranges, allowed values, and defaults. For example, it describes the domain_identifier pattern, max_results range, search_scope values, and pagination token constraints, adding significant meaning beyond the bare schema.

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 that the tool invokes the SearchTypes action to retrieve type definitions (asset types, form types, lineage node types) that match search criteria. It uses specific verbs and resources, and clearly distinguishes from sibling tools like 'search', 'search_listings', etc., which target different entities.

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?

The description explains what the tool does and its parameters, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'search', 'search_listings'). It lacks 'when not to use' or comparative context, leaving the agent to infer usage from purpose alone.

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