Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

create_collection

Create a new collection in Alteryx Server to organize and manage workflows, users, schedules, and credentials.

Instructions

Create a new collection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Implementation Reference

  • The core handler function in AYXMCPTools class that creates a new collection using the Alteryx CollectionsApi.
    def create_collection(self, name: str):
        """Create a new collection. To add a collection to a user, use the update_collection_name_or_owner function."""
        try:
            contract = server_client.CreateCollectionContract(name=name)
            api_response = self.collections_api.collections_create_collection(contract)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration decorator and wrapper function that delegates to the tools.create_collection method.
    @self.app.tool()
    def create_collection(name: str):
        """Create a new collection"""
        return self.tools.create_collection(name)
  • The input schema/model for CreateCollectionContract, defining the 'name' parameter as a string.
    class CreateCollectionContract(object):
        """NOTE: This class is auto generated by the swagger code generator program.
    
        Do not edit the class manually.
        """
    
        """
        Attributes:
          swagger_types (dict): The key is attribute name
                                and the value is attribute type.
          attribute_map (dict): The key is attribute name
                                and the value is json key in definition.
        """
        swagger_types = {"name": "str"}
    
        attribute_map = {"name": "name"}
    
        def __init__(self, name=None, _configuration=None):  # noqa: E501
            """CreateCollectionContract - a model defined in Swagger"""  # noqa: E501
            if _configuration is None:
                _configuration = Configuration()
            self._configuration = _configuration
    
            self._name = None
            self.discriminator = None
    
            self.name = name
    
        @property
        def name(self):
            """Gets the name of this CreateCollectionContract.  # noqa: E501
    
            The name of the new collection.  # noqa: E501
    
            :return: The name of this CreateCollectionContract.  # noqa: E501
            :rtype: str
            """
            return self._name
    
        @name.setter
        def name(self, name):
            """Sets the name of this CreateCollectionContract.
    
            The name of the new collection.  # noqa: E501
    
            :param name: The name of this CreateCollectionContract.  # noqa: E501
            :type: str
            """
            if self._configuration.client_side_validation and name is None:
                raise ValueError("Invalid value for `name`, must not be `None`")  # noqa: E501
    
            self._name = name
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create a new collection' which implies a write/mutation operation, but doesn't disclose any behavioral traits such as permissions required, whether it's idempotent, what happens on duplicate names, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise with just three words, which is appropriately sized for a simple tool. However, it's under-specified rather than efficiently informative—every word earns its place but more content is needed for completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is a mutation (create) with no annotations, 1 parameter at 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain what a collection is, the effects of creation, error conditions, or return values, leaving significant gaps for agent understanding.

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

Parameters3/5

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

The description adds no parameter information beyond what the input schema provides. With 0% schema description coverage and 1 parameter, the baseline is 4 for zero parameters, but since there is 1 parameter, the description fails to compensate. It doesn't explain the 'name' parameter's purpose, format, or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

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

The description 'Create a new collection' restates the tool name 'create_collection' in a tautological manner. It specifies the verb 'Create' and resource 'collection', but lacks any distinguishing details about what a collection is or how it differs from similar resources like workflows or schedules. No sibling differentiation is provided.

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 guidance is given on when to use this tool versus alternatives. Sibling tools like 'get_all_collections' or 'update_collection_name_or_owner' exist, but the description doesn't mention prerequisites, timing, or comparisons. Usage is implied only by the verb 'Create'.

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/jupiterbak/AYX-MCP-Wrapper'

If you have feedback or need assistance with the MCP directory API, please join our Discord server