V13 / BUNDLED SCENARIO

Calendar search

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

V13Pinned source · 7879e8b5740bExit: respond

Use this scenario

Run

Run calendar_search 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_search",
  "inputs": {
    "query": "your query"
  }
}
SCENARIO BLUEPRINT

Read the workflow.

calendar_search1 INPUTS / 1 TOOLS / 1 STEPS
01

Inputs

PARAMETERS
InputRequirementDefault value
queryRequiredNo 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_search_operation

    • query = {{query}}

    Save output as calendar.

05

Return to main

RESPOND EXIT

List the verified matching events concisely with dates and reminder times. Do not read internal IDs aloud unless requested.

The main agent receives the result and these instructions, then composes the final reply.

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

    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_search_operation

    Grants an existing tool.

    Writing example ↗
  7. 07
    <steps>

    Orders the chat turns.

    Writing example ↗
  8. 08
    <tool>calendar_search_operation

    Executes a declared host operation.

    Writing example ↗
  9. 09
    <input>query

    Binds a named operation or child input.

    Writing example ↗
  10. 10
    <exit>

    Lets the main agent respond.

    Writing example ↗