Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

reset_user_password

Reset passwords for Alteryx Server users by specifying their user ID to restore account access.

Instructions

Reset a user's password by their ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Implementation Reference

  • The core implementation of the reset_user_password tool. It checks if the user exists, calls the Alteryx API to reset the password, and returns the formatted response or error.
    def reset_user_password(self, user_id: str):
        """Reset a user's password 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_reset_user_password(user_id)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration using the @app.tool decorator, which exposes the tool and delegates execution to the underlying tools.reset_user_password method.
    @self.app.tool()
    def reset_user_password(user_id: str):
        """Reset a user's password by their ID"""
        return self.tools.reset_user_password(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. While 'reset' implies a mutation, it doesn't specify whether this requires admin privileges, if the user gets logged out, whether email notifications are sent, or what happens on failure. This leaves significant behavioral gaps for a security-sensitive operation.

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, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a tool with one parameter and no complex behavioral nuances to explain.

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 password reset tool with no annotations, no output schema, and 0% parameter documentation, the description is inadequate. It doesn't cover security implications, error conditions, return values, or parameter details that would be essential for safe and correct usage.

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 schema has 0% description coverage for its single parameter 'user_id', and the description provides no additional parameter information. It doesn't clarify what format the user_id should be (UUID, username, email?), where to find it, or if there are validation rules. This leaves the parameter meaning ambiguous.

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 action ('reset') and target resource ('user's password'), providing a specific verb+resource combination. However, it doesn't differentiate from potential sibling tools like 'update_user_details' or 'deactivate_user' that might also affect user accounts, so it falls short of a perfect score.

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 like 'update_user_details' or 'deactivate_user', nor does it mention prerequisites such as administrative permissions. It simply states what the tool does without contextual usage 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/jupiterbak/AYX-MCP-Wrapper'

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