V16 / BUNDLED SCENARIO

Schedule cancel

Schedule cancel: 1 ordered steps in Lilith V16, using schedule_cancel_operation. Read the exact bundled XML and its input and exit contracts.

V16Pinned source · 6df58cd3ed86Exit: copy

Use this scenario

Run

Run schedule_cancel 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": "schedule_cancel",
  "inputs": {
    "name": "your name"
  }
}
SCENARIO BLUEPRINT

Read the workflow.

schedule_cancel1 INPUTS / 1 TOOLS / 1 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
nameRequiredNo default
02

Agent instructions

SYSTEM PROMPT

Manage the schedule using the bound inputs. Call the provided operation exactly once with {}. Never invent success.

03

Tool access

CAPABILITIES
04

Ordered steps

EXECUTION
  1. 01
    CHAT TURN 01

    Call schedule_cancel_operation with {} now.

05

Return to main

COPY EXIT

Return the verified application result.

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

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

    Grants an existing tool.

    Writing example ↗
  7. 07
    <steps>

    Orders the chat turns.

    Writing example ↗
  8. 08
    <step 1>

    Cancel future firings.

    Writing example ↗
  9. 09
    <exit>

    Returns the output unchanged.

    Writing example ↗