Skip to main content
Glama

update_schedule

Update selected fields of an existing irrigation schedule without affecting other settings. Adjust timing, restrictions, or zones by specifying only the values to change.

Instructions

Partial-merge update of an existing schedule.

Only the fields you pass are changed. The current schedule is read first and your changes are overlaid onto its existing timing, restrictions, and zones, then sent as a single update — so omitting an argument leaves that aspect untouched. Field meanings match create_schedule / preview_schedule.

Recommended: call get_schedule first to review current values.

Args: schedule_id: Schedule UUID to update. name: New display name. enabled: New enabled state. schedule_type: FIXED, FLEX_MONTHLY, or FLEX_DAILY. start_time: Daily start time HH:MM (mutually exclusive with start_sun; supplying one replaces the other). start_sun: "SUNRISE" or "SUNSET". days: Days of week, e.g. ["MON", "WED", "FRI"]. Replaces the existing day restriction. Pass [] to clear it. annual_start: Annual window start MM-DD. Pass "" to clear. annual_end: Annual window end MM-DD. Pass "" to clear. smart_cycle: Let Rachio auto-calculate cycle/soak. cycle_soak: Enable manual cycle+soak. cycle_time_seconds: Cycle length in seconds. soak_time_seconds: Soak duration in seconds. zone_delay_time_seconds: Delay between zones. rain_delay_enabled: Enable rain-delay skipping. freeze_delay_enabled: Enable freeze-delay skipping. wind_delay_enabled: Enable wind-delay skipping. climate_skip: Enable climate/ET skipping. seasonal_shift: Enable seasonal runtime adjustment. zones: Zone entries to add or update, matched on device_id + zone_id. Each dict needs device_id and zone_id; watering_time (seconds) is required for new zones and optional when updating an existing one. Optional order_id, flex_aggression_coefficient, flex_runtime_coefficient. zone_ids_to_remove: Zone UUIDs to drop from the schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
nameNo
zonesNo
enabledNo
start_sunNo
annual_endNo
cycle_soakNo
start_timeNo
schedule_idYes
smart_cycleNo
annual_startNo
climate_skipNo
schedule_typeNo
seasonal_shiftNo
soak_time_secondsNo
cycle_time_secondsNo
rain_delay_enabledNo
wind_delay_enabledNo
zone_ids_to_removeNo
freeze_delay_enabledNo
zone_delay_time_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations provide readOnlyHint=false, destructiveHint=false; description adds critical detail about the partial-merge, non-destructive nature (except zone removal), and that omitting args leaves them untouched. No contradiction.

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?

Front-loaded with summary and behavior, followed by a concise recommendation, then a well-organized Args list. Every sentence is informative with no filler.

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

Completeness5/5

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

Given the complexity (21 parameters, no output schema shown), the description covers all essential aspects: purpose, behavior, parameter semantics, and usage recommendations. Output schema exists but does not need to be described.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing detailed explanations for all 21 parameters, including format constraints, mutual exclusivity, and special values (e.g., 'Pass [] to clear').

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

Purpose5/5

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

The description clearly states 'Partial-merge update of an existing schedule' which is a specific verb+resource. It further explains the overlay behavior and references sibling tools for field meanings, effectively distinguishing from create/preview.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Recommends calling 'get_schedule first to review current values', providing clear before-use guidance. It implicitly distinguishes from create_schedule and preview_schedule but lacks explicit when-not-to-use exclusions.

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/rwestergren/rachio-mcp'

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