Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

change_schedule_owner

Transfer schedule ownership to a different user by specifying the schedule ID and new owner ID in Alteryx Server.

Instructions

Change the owner of a schedule by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schedule_idYes
new_owner_idYes

Implementation Reference

  • Core handler function in AYXMCPTools class that implements changing a schedule's owner using the Alteryx V3 API. Fetches the schedule, updates the owner_id in UpdateScheduleContract, and calls schedules_update_schedule.
    def change_schedule_owner(self, schedule_id: str, new_owner_id: str):
        """Change the owner of a schedule by its ID"""
        try:
            schedule = self.schedules_api.schedules_get_schedule(schedule_id)
            if not schedule:
                return "Error: Schedule not found"
            
            contract = server_client.UpdateScheduleContract(
                workflow_id=schedule.workflow_id,
                owner_id=new_owner_id if new_owner_id else schedule.owner_id,
                iteration=schedule.iteration,
                name=schedule.name,
                comment=schedule.comment,
                priority=schedule.priority,
                worker_tag=schedule.worker_tag,
                enabled=schedule.enabled,
                credential_id=schedule.credential_id,
                time_zone=schedule.time_zone,
                questions=schedule.questions,
            )
            api_response = self.schedules_api.schedules_update_schedule(schedule_id, contract)
            return pprint.pformat(api_response)
        except ApiException as e:
            return f"Error: {e}"
  • MCP tool registration in MCPAlteryxServer class. Decorates the wrapper function with @self.app.tool() and delegates to the tools instance's change_schedule_owner method.
    @self.app.tool()
    def change_schedule_owner(schedule_id: str, new_owner_id: str):
        """Change the owner of a schedule by its ID"""
        return self.tools.change_schedule_owner(schedule_id, new_owner_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. It indicates a mutation action ('Change') but lacks details on permissions required, whether the change is reversible, error conditions (e.g., invalid IDs), or side effects. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence contributes directly to understanding the tool's function, making it appropriately concise.

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 complexity of a mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks critical information such as behavioral traits, parameter semantics, and expected outcomes, which are essential for safe and effective tool invocation.

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 implies parameters for schedule ID and new owner ID, aligning with the two parameters in the schema. However, with 0% schema description coverage, it does not add meaning beyond naming (e.g., format of IDs, validation rules). The baseline is 3 since the schema covers the parameters structurally, but the description fails to compensate for the lack of semantic details.

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 ('Change the owner') and target resource ('a schedule by its ID'), providing a specific verb+resource combination. However, it does not explicitly distinguish this tool from sibling tools like 'update_schedule_name_or_comment' or 'transfer_all_assets', which might involve ownership changes in different contexts.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., permissions needed), exclusions, or comparisons to sibling tools such as 'update_schedule_name_or_comment' or 'transfer_all_assets', leaving the agent to infer usage context.

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