V18 / BUNDLED SCENARIO

Calendar delete

Calendar delete: 1 ordered steps in Lilith V18, using calendar_delete_operation. Read the exact bundled XML and its input and exit contracts.

V18Pinned source · 8d896b8a86e5Exit: copy

Use this scenario

Run

Run calendar_delete 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_delete",
  "inputs": {
    "id": "your id"
  }
}
SCENARIO BLUEPRINT

Read the workflow.

calendar_delete1 INPUTS / 1 TOOLS / 1 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
idRequiredNo default
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_delete_operation

    • id = {{id}}

    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
    <systemPrompt>

    Sets the child's instructions.

    Writing example ↗
  5. 05
    <tools>

    Defines available capabilities.

    Writing example ↗
  6. 06
    <allow>calendar_delete_operation

    Grants an existing tool.

    Writing example ↗
  7. 07
    <steps>

    Orders the chat turns.

    Writing example ↗
  8. 08
    <tool>calendar_delete_operation

    Executes a declared host operation.

    Writing example ↗
  9. 09
    <input>id

    Binds a named operation or child input.

    Writing example ↗
  10. 10
    <exit>

    Returns the output unchanged.

    Writing example ↗