Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

deactivate_user

Deactivate a user account in Alteryx Server by providing the user ID to disable access and manage permissions.

Instructions

Deactivate a user account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Implementation Reference

  • Core handler function in AYXMCPTools class that implements the logic for deactivating a user: checks if user exists, calls the Alteryx Users API users_deactivate_user, and formats the response.
    def deactivate_user(self, user_id: str):
        """Deactivate a user by their ID"""
        try:
            user = self.users_api.users_get_user(user_id)
            if not user:
                return "Error: User not found"
            api_response = self.users_api.users_deactivate_user(user_id)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration using @self.app.tool() decorator in the register_tools method of the MCP server, which delegates execution to the tools.deactivate_user method.
    @self.app.tool()
    def deactivate_user(user_id: str):
        """Deactivate a user account"""
        return self.tools.deactivate_user(user_id)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Deactivate' implies a destructive/mutative action, but it doesn't specify what deactivation entails (e.g., disables login, preserves data, reversible?), permissions required, side effects, or error conditions. This is inadequate for a tool that likely modifies system state.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient. No structural issues exist given its brevity and clarity.

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?

For a destructive tool with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks critical details: what deactivation does, success/error responses, prerequisites, and implications. This leaves significant gaps for an agent to use the tool safely and effectively.

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 the schema, which has 0% description coverage. However, with only one parameter ('user_id'), the baseline is 4, but it's reduced to 3 because the description doesn't clarify what 'user_id' represents (e.g., format, source, uniqueness) or provide any context to compensate for the schema gap.

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

Purpose4/5

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

The description clearly states the verb ('Deactivate') and resource ('a user account'), making the purpose unambiguous. It distinguishes from obvious siblings like 'activate_user' (not listed) but doesn't explicitly differentiate from similar tools like 'update_user_details' or 'reset_user_password' that might also affect user status.

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 provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., user must exist, permissions required), exclusions (e.g., cannot deactivate own account), or related tools like 'update_user_details' for partial deactivation. The description alone gives no context for decision-making.

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