Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

get_all_user_assets

Retrieve all assets associated with a specific user from the Alteryx server, including workflows, collections, and other resources.

Instructions

Get all the assets for a user

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Implementation Reference

  • The core handler function that implements the tool logic by calling the Alteryx server API to retrieve all assets for a given user ID and formatting the response.
    def get_all_user_assets(self, user_id: str):
        """Get all the assets for a user"""
        try:
            api_response = self.users_api.users_get_users_assets(user_id)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • The MCP tool registration decorator and wrapper function that registers the tool and delegates execution to the underlying tools instance.
    @self.app.tool()
    def get_all_user_assets(user_id: str):
        """Get all the assets for a user"""
        return self.tools.get_all_user_assets(user_id)
Behavior2/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 of behavioral disclosure. It states 'Get all the assets' but does not clarify if this is a read-only operation, what permissions are required, whether it returns paginated results, or the format of the output (e.g., list of asset objects). This leaves significant gaps in understanding the tool's behavior and limitations.

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 a single, straightforward sentence with no unnecessary words, making it highly concise and front-loaded. It efficiently communicates the core purpose without redundancy or structural issues.

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's complexity (a read operation with 1 parameter), lack of annotations, no output schema, and low schema coverage, the description is incomplete. It fails to address key aspects like output format, error conditions, or behavioral traits, leaving the agent with inadequate information for reliable use.

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?

The input schema has 1 parameter (user_id) with 0% description coverage, meaning the schema provides no semantic details. The description adds minimal value by implying the parameter is for a user, but it does not specify the user_id format (e.g., UUID, email), constraints, or examples. This insufficiently compensates for the low schema coverage.

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

Purpose3/5

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

The description 'Get all the assets for a user' clearly states the action (get) and resource (assets for a user), making the purpose understandable. However, it lacks specificity about what 'assets' entail (e.g., workflows, schedules, collections) and does not distinguish this tool from sibling tools like 'get_user_assets_by_type' or 'transfer_all_assets', leaving ambiguity in scope.

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. It does not mention prerequisites (e.g., user existence), exclusions, or compare it to siblings such as 'get_user_assets_by_type' (which filters by asset type) or 'get_all_collections' (which might overlap). Without such context, usage is implied but not explicitly defined.

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