Use this scenario
Run
Run message_channels scenario.
Use run_scenario with the saved scenario name and string-valued inputs. Required values are requested before execution.
View invocation JSON
{
"scenario_name": "message_channels",
"inputs": {
"after": ""
}
}Inputs
PARAMETERS| Input | Requirement | Default value |
|---|---|---|
after | Optional | |
Agent instructions
SYSTEM PROMPTList configured channel nicknames from actual bridge data. Dummy Discord-style channels are local simulations, not Discord connections. A page contains at most 20 channels; pass the last nickname as after to read more.
Tool access
CAPABILITIESmessage_channels_operation— selected from this version's tool catalog.
Ordered steps
EXECUTION- 01BOUND OPERATION / HOST EXECUTED
message_channels_operationafter= {{after}}
Save output as
receipt.
Return to main
RESPOND EXITReport the actual configured nicknames and adapters. Clearly label dummy channels as local tests. Do not invent accounts or delivery.
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="3" id="message_channels" title="List messaging connections">
<inputs><input name="after" default="" /></inputs>
<systemPrompt>List configured channel nicknames from actual bridge data. Dummy Discord-style channels are local simulations, not Discord connections. A page contains at most 20 channels; pass the last nickname as after to read more.</systemPrompt>
<tools><allow name="message_channels_operation" /></tools>
<steps><tool name="message_channels_operation" result="receipt"><input name="after" value="{{after}}" /></tool></steps>
<exit mode="respond">Report the actual configured nicknames and adapters. Clearly label dummy channels as local tests. Do not invent accounts or delivery.</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>afterProvides an optional value.
- 04Writing example ↗
<systemPrompt>Sets the child's instructions.
- 05Writing example ↗
<tools>Defines available capabilities.
- 06Writing example ↗
<allow>message_channels_operationGrants an existing tool.
- 07Writing example ↗
<steps>Orders the chat turns.
- 08Writing example ↗
<tool>message_channels_operationExecutes a declared host operation.
- 09Writing example ↗
<input>afterBinds a named operation or child input.
- 10Writing example ↗
<exit>Lets the main agent respond.