Use this scenario
Run
Run schedule_create 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_create",
"inputs": {
"name": "your name",
"kind": "timer",
"seconds": "0",
"cron": "",
"timezone": "",
"message": "",
"scenario": "",
"inputs_json": "{}"
}
}Inputs
PARAMETERS| Input | Requirement | Default value |
|---|---|---|
name | Required | No default |
kind | Optional | timer |
seconds | Optional | 0 |
cron | Optional | |
timezone | Optional | |
message | Optional | |
scenario | Optional | |
inputs_json | Optional | {} |
Agent instructions
SYSTEM PROMPTManage the schedule using the bound inputs. Call the provided operation exactly once with {}. Never invent success.
Tool access
CAPABILITIESschedule_create_operation— selected from this version's tool catalog.
Ordered steps
EXECUTION- 01CHAT TURN 01
Call schedule_create_operation with {} now.
Return to main
COPY EXITReturn the verified application result.
The final text returns without model rewriting. Bound operation scenarios return application results; pending changes still require host approval.
Complete XML, including any embedded C#. Copy it without changing the file's contents.
<scenario schemaVersion="1" id="schedule_create" title="Schedule create">
<inputs><input name="name" required="true" /><input name="kind" default="timer" /><input name="seconds" default="0" /><input name="cron" default="" /><input name="timezone" default="" /><input name="message" default="" /><input name="scenario" default="" /><input name="inputs_json" default="{}" /></inputs>
<systemPrompt>Manage the schedule using the bound inputs. Call the provided operation exactly once with {}. Never invent success.</systemPrompt>
<tools><allow name="schedule_create_operation" /></tools>
<steps><step>Call schedule_create_operation with {} now.</step></steps>
<exit mode="copy">Return the verified application result.</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 ↗
<input>kindProvides an optional value.
- 05Writing example ↗
<input>secondsProvides an optional value.
- 06Writing example ↗
<input>cronProvides an optional value.
- 07Writing example ↗
<input>timezoneProvides an optional value.
- 08Writing example ↗
<input>messageProvides an optional value.
- 09Writing example ↗
<input>scenarioProvides an optional value.
- 10Writing example ↗
<input>inputs_jsonProvides an optional value.
- 11Writing example ↗
<systemPrompt>Sets the child's instructions.
- 12Writing example ↗
<tools>Defines available capabilities.
- 13Writing example ↗
<allow>schedule_create_operationGrants an existing tool.
- 14Writing example ↗
<steps>Orders the chat turns.
- 15Writing example ↗
<step 1>Create or propose a schedule.
- 16Writing example ↗
<exit>Returns the output unchanged.