A secretary you ask in ordinary words

The neighbouring calendar scenarios each answer one question, and the sequence is fixed by the graph: query, then answer. Here it is the other way round — the tools belong to the model, and it decides what to call and how many times.

What is inside

1. A question about the schedule — the entry.
2. The secretary — the agent.
3. Calendar tools are wired with link_extension: list calendars, query events, check busy time.
4. Conversation memory lets you ask “and next week?” without repeating yourself.

That is why one scenario covers a whole family of questions. The price is predictability: the model may call the calendar twice, or answer from the conversation, and a turn costs more than in a scenario with a fixed sequence.

What to set up for yourself

• The tool list. Only reading is enabled. Create and delete are switched on in the same place, but then the bot can change your calendar on one sentence — start with reading.
• The prompt. It carries a rule about confirming before creating a meeting. You will want that the moment you enable writing.
• Memory. The window is small; for long conversations about a schedule it is worth raising, remembering that every turn in the window is paid for on every later question.

What to connect

A calendar over CalDAV. Write access is not needed while the tool list is read-only.