Set a local spam sender rule

Use this scenario

Run

Run email_spam 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": "email_spam",
  "inputs": {
    "nickname": "your nickname",
    "sender": "your sender",
    "blocked": "true"
  }
}

email_spam3 INPUTS / 1 TOOLS / 1 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`nickname`	Required	`No default`
`sender`	Required	`No default`
`blocked`	Optional	`true`

Agent instructions

SYSTEM PROMPT

Only propose this rule when the user explicitly asks to mark a sender as Spam or unblock them. Never infer spam from message content. This affects local sections only, never Gmail.

Tool access

CAPABILITIES

email_spam_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
BOUND OPERATION / HOST EXECUTED
email_spam_operation
- nickname = {{nickname}}
- sender = {{sender}}
- blocked = {{blocked}}
Save output as proposal.

Return to main

COPY EXIT

Return the exact host proposal and confirmation command unchanged.

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="email_spam" title="Set a local spam sender rule">
  <inputs><input name="nickname" required="true" /><input name="sender" required="true" /><input name="blocked" default="true" /></inputs>
  <systemPrompt>Only propose this rule when the user explicitly asks to mark a sender as Spam or unblock them. Never infer spam from message content. This affects local sections only, never Gmail.</systemPrompt>
  <tools><allow name="email_spam_operation" /></tools>
  <steps><tool name="email_spam_operation" result="proposal"><input name="nickname" value="{{nickname}}" /><input name="sender" value="{{sender}}" /><input name="blocked" value="{{blocked}}" /></tool></steps>
  <exit mode="copy">Return the exact host proposal and confirmation command unchanged.</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>sender
Requires a supplied value.
Writing example ↗
05
<input>blocked
Provides an optional value.
Writing example ↗
06
<systemPrompt>
Sets the child's instructions.
Writing example ↗
07
<tools>
Defines available capabilities.
Writing example ↗
08
<allow>email_spam_operation
Grants an existing tool.
Writing example ↗
09
<steps>
Orders the chat turns.
Writing example ↗
10
<tool>email_spam_operation
Executes a declared host operation.
Writing example ↗
11
<input>nickname
Binds a named operation or child input.
Writing example ↗
12
<input>sender
Binds a named operation or child input.
Writing example ↗
13
<input>blocked
Binds a named operation or child input.
Writing example ↗
14
<exit>
Returns the output unchanged.
Writing example ↗

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