Prepare and send an outgoing message

Use this scenario

Run

Run message_send 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": "message_send",
  "inputs": {
    "nickname": "your nickname",
    "room": "your room",
    "text": "your text",
    "reply_to": ""
  }
}

message_send4 INPUTS / 1 TOOLS / 1 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`nickname`	Required	`No default`
`room`	Required	`No default`
`text`	Required	`No default`
`reply_to`	Optional

Agent instructions

SYSTEM PROMPT

Prepare exactly the destination and text supplied by the local user or trusted reply workflow. Never select another recipient or add content. The host enforces boot-fixed Ask/YOLO and exact pending approvals; a scenario cannot approve itself.

Tool access

CAPABILITIES

message_send_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
BOUND OPERATION / HOST EXECUTED
message_send_operation
- nickname = {{nickname}}
- room = {{room}}
- text = {{text}}
- reply_to = {{reply_to}}
Save output as receipt.

Return to main

COPY EXIT

Return the exact host receipt; never claim external delivery for a dummy channel.

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.

XMLStructureInputsTools / C#StepsExit

<scenario schemaVersion="3" id="message_send" title="Prepare and send an outgoing message">
  <inputs><input name="nickname" required="true" /><input name="room" required="true" /><input name="text" required="true" /><input name="reply_to" default="" /></inputs>
  <systemPrompt>Prepare exactly the destination and text supplied by the local user or trusted reply workflow. Never select another recipient or add content. The host enforces boot-fixed Ask/YOLO and exact pending approvals; a scenario cannot approve itself.</systemPrompt>
  <tools><allow name="message_send_operation" /></tools>
  <steps><tool name="message_send_operation" result="receipt"><input name="nickname" value="{{nickname}}" /><input name="room" value="{{room}}" /><input name="text" value="{{text}}" /><input name="reply_to" value="{{reply_to}}" /></tool></steps>
  <exit mode="copy">Return the exact host receipt; never claim external delivery for a dummy channel.</exit>
</scenario>

Download XML ↓

EVERY XML ELEMENT / IN FILE ORDER

Every part, briefly.

Short explanations of every element and chat step in this scenario.

01
<scenario>
Names and versions the workflow.
Writing example ↗
02
<inputs>
Declares input values.
Writing example ↗
03
<input>nickname
Requires a supplied value.
Writing example ↗
04
<input>room
Requires a supplied value.
Writing example ↗
05
<input>text
Requires a supplied value.
Writing example ↗
06
<input>reply_to
Provides an optional value.
Writing example ↗
07
<systemPrompt>
Sets the child's instructions.
Writing example ↗
08
<tools>
Defines available capabilities.
Writing example ↗
09
<allow>message_send_operation
Grants an existing tool.
Writing example ↗
10
<steps>
Orders the chat turns.
Writing example ↗
11
<tool>message_send_operation
Executes a declared host operation.
Writing example ↗
12
<input>nickname
Binds a named operation or child input.
Writing example ↗
13
<input>room
Binds a named operation or child input.
Writing example ↗
14
<input>text
Binds a named operation or child input.
Writing example ↗
15
<input>reply_to
Binds a named operation or child input.
Writing example ↗
16
<exit>
Returns the output unchanged.
Writing example ↗

Write a scenario, step by step ↗How sub-agents work ↗