Use this scenario
Run
Run schedule_peek scenario.
Use run_scenario with the saved scenario name and string-valued inputs. Required values are requested before execution.
View invocation JSON
{
"scenario_name": "schedule_peek",
"inputs": {
"name": "your name"
}
}Watch this version
Inputs
PARAMETERS| Input | Requirement | Default value |
|---|---|---|
name | Required | No default |
Agent instructions
SYSTEM PROMPTManage the schedule using the bound inputs. Call the provided operation exactly once with {}. Never invent success.
Tool access
CAPABILITIESschedule_peek_operation— selected from this version's tool catalog.
Ordered steps
EXECUTION- 01CHAT TURN 01
Call schedule_peek_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_peek" title="Schedule peek">
<inputs><input name="name" required="true" /></inputs>
<systemPrompt>Manage the schedule using the bound inputs. Call the provided operation exactly once with {}. Never invent success.</systemPrompt>
<tools><allow name="schedule_peek_operation" /></tools>
<steps><step>Call schedule_peek_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 ↗
<input>nameRequires a supplied value.
- 04Writing example ↗
<systemPrompt>Sets the child's instructions.
- 05Writing example ↗
<tools>Defines available capabilities.
- 06Writing example ↗
<allow>schedule_peek_operationGrants an existing tool.
- 07Writing example ↗
<steps>Orders the chat turns.
- 08Writing example ↗
<step 1>Check remaining time.
- 09Writing example ↗
<exit>Lets the main agent respond.