Skip to main content
Glama
jupiterbak

AYX-MCP-Wrapper

by jupiterbak

deactivate_schedule

Stop automated workflow execution by disabling a specific schedule in Alteryx Server using its unique identifier.

Instructions

Deactivate a schedule by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
schedule_idYes

Implementation Reference

  • Core handler implementation for the 'deactivate_schedule' tool. Fetches the current schedule, creates an UpdateScheduleContract with enabled=False, and updates the schedule via the API.
    def deactivate_schedule(self, schedule_id: str):
        """Deactivate 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=schedule.owner_id,
                iteration=schedule.iteration,
                name=schedule.name,
                comment=schedule.comment,
                priority=schedule.priority,
                worker_tag=schedule.worker_tag,
                enabled=False,
                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 for 'deactivate_schedule'. This decorator registers the tool with the MCP server and delegates execution to the underlying tools.deactivate_schedule method.
    @self.app.tool()
    def deactivate_schedule(schedule_id: str):
        """Deactivate a schedule by its ID"""
        return self.tools.deactivate_schedule(schedule_id)
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('deactivate') but doesn't clarify what deactivation entails (e.g., whether it's reversible, if it affects associated jobs, permission requirements, or side effects). This leaves critical behavioral traits unspecified for a mutation 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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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 mutation tool with no annotations, no output schema, and minimal parameter guidance, the description is incomplete. It lacks information on what deactivation means, expected outcomes, error conditions, or how it fits within the broader system context, leaving significant gaps for an agent to use it 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 mentions 'by its ID', which aligns with the single 'schedule_id' parameter in the schema. However, with 0% schema description coverage, the description doesn't add meaningful details about parameter format, constraints, or where to obtain the ID. It provides basic mapping but minimal enhancement over the bare schema.

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 schedule'), making the purpose unambiguous. It distinguishes from obvious alternatives like 'activate_schedule' by specifying the opposite action, though it doesn't explicitly differentiate from all sibling tools like 'delete_collection' or 'deactivate_user'.

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, prerequisites, or contextual constraints. It doesn't mention when deactivation is appropriate compared to deletion or other schedule modifications, leaving usage entirely implicit.

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