Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

get_all_users

Retrieve all user accounts from the Alteryx server to manage access permissions and user administration.

Instructions

Get the list of all users of the Alteryx server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools.py:355-361 (handler)
    Core handler function that retrieves all users from the Alteryx server API using users_api.users_get_users() and formats the response.
    def get_all_users(self):
    """Get the list of all users of the Alteryx server"""
    try:
        api_response = self.users_api.users_get_users()
        return pprint.pformat(api_response)
    except ApiException as e:
        return f"Error: {e}"
  • src/mcp_server.py:231-234 (registration)
    MCP tool registration decorator and wrapper function that delegates execution to self.tools.get_all_users().
    @self.app.tool()
def get_all_users():
    """Get the list of all users of the Alteryx server"""
    return self.tools.get_all_users()

Tool Definition Quality

B3.2/5.0
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 the action but lacks details on permissions required, rate limits, pagination, or return format. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool has 0 parameters and no output schema, the description is minimally complete for a simple retrieval tool. However, without annotations, it lacks details on behavioral aspects like authentication needs or response structure, which could be important for an agent to use it effectively in context.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly avoids mentioning any. A baseline of 4 is appropriate as it doesn't mislead or omit necessary information about inputs.

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 ('Get') and resource ('list of all users of the Alteryx server'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_user_by_email' or 'get_user_by_id', which are more targeted user retrieval methods.

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 doesn't mention that this retrieves all users without filtering, unlike sibling tools that fetch users by specific criteria (e.g., email, ID, name), leaving the agent to infer usage from context 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/jupiterbak/AYX-MCP-Wrapper'

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