Use this scenario
Run
Run schedule_pending scenario.
Watch this version
Inputs
PARAMETERSThis scenario declares no inputs.
Agent instructions
SYSTEM PROMPTManage the schedule using the bound inputs. Call the provided operation exactly once with {}. Never invent success.
Tool access
CAPABILITIESschedule_pending_operation— selected from this version's tool catalog.
Ordered steps
EXECUTION- 01CHAT TURN 01
Call schedule_pending_operation with {} now.
Return to main
RESPOND EXITAnswer the user using the verified schedule status, including remaining_seconds or next UTC time when relevant. Do not invent an active timer.
The main agent receives the result and these instructions, then composes the final reply.
Complete XML, including any embedded C#. Copy it without changing the file's contents.
<scenario schemaVersion="1" id="schedule_pending" title="Schedule pending">
<inputs></inputs>
<systemPrompt>Manage the schedule using the bound inputs. Call the provided operation exactly once with {}. Never invent success.</systemPrompt>
<tools><allow name="schedule_pending_operation" /></tools>
<steps><step>Call schedule_pending_operation with {} now.</step></steps>
<exit mode="respond">Answer the user using the verified schedule status, including remaining_seconds or next UTC time when relevant. Do not invent an active timer.</exit>
</scenario>
Every part, briefly.
Short explanations of every element and chat step in this scenario.
- 01Writing example ↗
<scenario>Names and versions the workflow.
- 02Writing example ↗
<inputs>Declares input values.
- 03Writing example ↗
<systemPrompt>Sets the child's instructions.
- 04Writing example ↗
<tools>Defines available capabilities.
- 05Writing example ↗
<allow>schedule_pending_operationGrants an existing tool.
- 06Writing example ↗
<steps>Orders the chat turns.
- 07Writing example ↗
<step 1>List proposed schedule changes.
- 08Writing example ↗
<exit>Lets the main agent respond.