Skip to main content
Glama
espressif

ESP RainMaker MCP Server

Official
by espressif

set_schedule

Manage schedules for IoT nodes: add, edit, remove, enable, or disable time-based triggers and actions across single or multiple devices.

Instructions

Manage schedules for one or more nodes.

Parameters:

  • node_id: Single node ID or comma-separated list of node IDs (e.g., "node1" or "node1,node2,node3")

  • operation: Operation to perform (add, edit, remove, enable, disable)

  • schedule_id: Schedule ID (required for edit, remove, enable, disable operations)

  • name: Schedule name (required for add operation, optional for edit)

  • trigger: Dictionary defining when to trigger (required for add, optional for edit)

  • action: Dictionary defining what to do (required for add, optional for edit)

  • info: Additional information for the schedule (optional)

  • flags: General purpose flags for the schedule (optional)

When multiple node IDs are provided:

  • For 'add' operations: Creates the same schedule on all specified nodes with a common schedule ID

  • For 'edit/remove/enable/disable' operations: Applies the operation to the specified schedule on all nodes

  • This is useful for bulk schedule management across multiple devices

TRIGGER FORMAT GUIDE: Time-based triggers use these fields:

  • "m": Minutes since midnight (0-1439). Example: 480 = 8:00 AM, 1110 = 6:30 PM

  • "d": Day bitmap for which days to trigger:

    • 31 = Weekdays (Mon-Fri)

    • 96 = Weekends (Sat-Sun)

    • 127 = Every day

    • 0 = One-time only

    • Individual days: 1=Mon, 2=Tue, 4=Wed, 8=Thu, 16=Fri, 32=Sat, 64=Sun

  • "dd": Day of month (1-31)

  • "mm": Month bitmap (4095 = all months)

  • "rsec": Relative seconds from now

  • "ts": Exact Unix timestamp

COMMON TRIGGER EXAMPLES:

  • Daily 8:00 AM: {"m": 480, "d": 127}

  • Weekdays 6:30 PM: {"m": 1110, "d": 31}

  • Weekends 10:00 AM: {"m": 600, "d": 96}

  • One-time 7:00 PM: {"m": 1140, "d": 0}

  • 15th of every month at noon: {"m": 720, "dd": 15, "mm": 4095}

  • In 1 hour: {"rsec": 3600}

ACTION EXAMPLES:

  • Turn on light: {"Light": {"Power": true}}

  • Set brightness: {"Light": {"Power": true, "Brightness": 80}}

  • Control thermostat: {"Thermostat": {"Power": true, "Temperature": 22}}

NOTE: Action keys use device type names (like "Light") not display names. Use get_node_details to see device types in config.devices[].name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYes
operationYes
schedule_idNo
nameNo
triggerNo
actionNo
infoNo
flagsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description details the effects of each operation and multi-node behavior, and warns about action keys using device type names. However, with no annotations, it lacks disclosure on error handling, validation, or rate limits, leaving some behavioral aspects implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is well-structured with clear sections and examples, front-loading the purpose. Although somewhat lengthy due to the trigger guide, the detail is necessary for correct usage.

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 tool's complexity (eight parameters, no annotations), the description is highly complete: it covers parameter details, multi-node behavior, trigger format with examples, action format, and a note on device types. An output schema exists, so return values are not needed.

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 explaining each parameter's purpose, required operations, and providing detailed format guides for trigger and action parameters, adding significant meaning beyond the schema.

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 'Manage schedules for one or more nodes' and lists specific operations (add, edit, remove, enable, disable), providing a specific verb and resource. It distinguishes from sibling tools like get_schedules (read-only) and set_params (different purpose).

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?

The description explains when to use each operation and parameter requirements, and provides guidance for multi-node behavior. However, it does not explicitly mention when not to use the tool or suggest alternative tools for related tasks.

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/espressif/esp-rainmaker-mcp'

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