Read local email sections

Use this scenario

Run

Run email_sections 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_sections",
  "inputs": {
    "nickname": "your nickname"
  }
}

Watch this version

V13 / Gemma 4 ↗

email_sections1 INPUTS / 1 TOOLS / 1 STEPS

Inputs

PARAMETERS

Input	Requirement	Default value
`nickname`	Required	`No default`

Agent instructions

SYSTEM PROMPT

Report local saved Shopping/Inbox classifications and explicitly blocked senders only. These are local sections, not Gmail folders. Classifications cover messages analyzed so far, not the whole mailbox. Identifiers are validity:UID pairs.

Tool access

CAPABILITIES

email_sections_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
BOUND OPERATION / HOST EXECUTED
email_sections_operation
- nickname = {{nickname}}
Save output as sections.

Return to main

RESPOND EXIT

Report the requested local sections and blocked senders faithfully. Use actual message IDs with email_read only if more detail is requested; do not invent subjects.

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.

XMLStructureInputsTools / C#StepsExit

<scenario schemaVersion="3" id="email_sections" title="Read local email sections">
  <inputs><input name="nickname" required="true" /></inputs>
  <systemPrompt>Report local saved Shopping/Inbox classifications and explicitly blocked senders only. These are local sections, not Gmail folders. Classifications cover messages analyzed so far, not the whole mailbox. Identifiers are validity:UID pairs.</systemPrompt>
  <tools><allow name="email_sections_operation" /></tools>
  <steps><tool name="email_sections_operation" result="sections"><input name="nickname" value="{{nickname}}" /></tool></steps>
  <exit mode="respond">Report the requested local sections and blocked senders faithfully. Use actual message IDs with email_read only if more detail is requested; do not invent subjects.</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
<systemPrompt>
Sets the child's instructions.
Writing example ↗
05
<tools>
Defines available capabilities.
Writing example ↗
06
<allow>email_sections_operation
Grants an existing tool.
Writing example ↗
07
<steps>
Orders the chat turns.
Writing example ↗
08
<tool>email_sections_operation
Executes a declared host operation.
Writing example ↗
09
<input>nickname
Binds a named operation or child input.
Writing example ↗
10
<exit>
Lets the main agent respond.
Writing example ↗

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