Wymcp tool schedules — adding, listing, updating and removing the standing instructions YmerNode.Schedules fires, and listing and stopping the watches the references tool starts.

A thin boundary over that context, wiring only the framework's callbacks. What a schedule is, what add refuses and what a firing skips live in the context's own moduledoc.

Destructive and open-world, like YmerNode.Mcp.Tools.Scripts. The tool itself runs nothing, but what it adds runs a script's action later — unattended, for as long as the schedule lives — and a script reaches the network with the node's own permissions.

Why it is a separate tool

Adding a schedule grants runs nobody will be there to see, up to 90 days of them. A tool of its own is what lets a client run what has been accepted without being able to set it running unattended: a per-tool permission the person sets once. That is why description/0 carries a line addressed to that person, as YmerNode.Mcp.Tools.ScriptAuthor's does.