V13 / BUNDLED SCENARIO

Calendar update

Calendar update: 1 ordered steps in Lilith V13, using calendar_update_operation. Read the exact bundled XML and its input and exit contracts.

V13Pinned source · 7879e8b5740bExit: copy

Use this scenario

Run

Run calendar_update scenario.

Use run_scenario with the saved scenario name and string-valued inputs. Required values are requested before execution.

View invocation JSON
JSON
{
  "scenario_name": "calendar_update",
  "inputs": {
    "id": "your id",
    "title": "your title",
    "date": "your date",
    "time": "",
    "timezone": "",
    "reminder": "your reminder",
    "notes": "",
    "source": ""
  }
}
SCENARIO BLUEPRINT

Read the workflow.

calendar_update8 INPUTS / 1 TOOLS / 1 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
idRequiredNo default
titleRequiredNo default
dateRequiredNo default
timeOptional
timezoneOptional
reminderRequiredNo default
notesOptional
sourceOptional
02

Agent instructions

SYSTEM PROMPT

Use the declared calendar operation. Never invent calendar events or claim unapproved writes.

03

Tool access

CAPABILITIES
04

Ordered steps

EXECUTION
  1. 01
    BOUND OPERATION / HOST EXECUTED

    calendar_update_operation

    • id = {{id}}
    • title = {{title}}
    • date = {{date}}
    • time = {{time}}
    • timezone = {{timezone}}
    • reminder = {{reminder}}
    • notes = {{notes}}
    • source = {{source}}

    Save output as calendar.

05

Return to main

COPY EXIT

Return the verified result unchanged.

The final text returns without model rewriting. Bound operation scenarios return application results; pending changes still require host approval.

EVERY XML ELEMENT / IN FILE ORDER

Every part, briefly.

Short explanations of every element and chat step in this scenario.

  1. 01
    <scenario>

    Names and versions the workflow.

    Writing example ↗
  2. 02
    <inputs>

    Declares input values.

    Writing example ↗
  3. 03
    <input>id

    Requires a supplied value.

    Writing example ↗
  4. 04
    <input>title

    Requires a supplied value.

    Writing example ↗
  5. 05
    <input>date

    Requires a supplied value.

    Writing example ↗
  6. 06
    <input>time

    Provides an optional value.

    Writing example ↗
  7. 07
    <input>timezone

    Provides an optional value.

    Writing example ↗
  8. 08
    <input>reminder

    Requires a supplied value.

    Writing example ↗
  9. 09
    <input>notes

    Provides an optional value.

    Writing example ↗
  10. 10
    <input>source

    Provides an optional value.

    Writing example ↗
  11. 11
    <systemPrompt>

    Sets the child's instructions.

    Writing example ↗
  12. 12
    <tools>

    Defines available capabilities.

    Writing example ↗
  13. 13
    <allow>calendar_update_operation

    Grants an existing tool.

    Writing example ↗
  14. 14
    <steps>

    Orders the chat turns.

    Writing example ↗
  15. 15
    <tool>calendar_update_operation

    Executes a declared host operation.

    Writing example ↗
  16. 16
    <input>id

    Binds a named operation or child input.

    Writing example ↗
  17. 17
    <input>title

    Binds a named operation or child input.

    Writing example ↗
  18. 18
    <input>date

    Binds a named operation or child input.

    Writing example ↗
  19. 19
    <input>time

    Binds a named operation or child input.

    Writing example ↗
  20. 20
    <input>timezone

    Binds a named operation or child input.

    Writing example ↗
  21. 21
    <input>reminder

    Binds a named operation or child input.

    Writing example ↗
  22. 22
    <input>notes

    Binds a named operation or child input.

    Writing example ↗
  23. 23
    <input>source

    Binds a named operation or child input.

    Writing example ↗
  24. 24
    <exit>

    Returns the output unchanged.

    Writing example ↗