List retained project revisions

Use this scenario

Run

Run project_backups 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": "project_backups",
  "inputs": {
    "name": "your name"
  }
}

Watch this version

V13 / Gemma 4 ↗

project_backups1 INPUTS / 1 TOOLS / 1 STEPS

Inputs

PARAMETERS

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

Agent instructions

SYSTEM PROMPT

List only retained revisions associated with the requested managed project. Do not execute code or restore files.

Tool access

CAPABILITIES

project_backups_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
BOUND OPERATION / HOST EXECUTED
project_backups_operation
- name = {{name}}
Save output as backups.

Return to main

COPY EXIT

Return retained backup IDs unchanged. No execution or changes occurred.

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="project_backups" title="List retained project revisions">
  <inputs><input name="name" required="true" /></inputs>
  <systemPrompt>List only retained revisions associated with the requested managed project. Do not execute code or restore files.</systemPrompt>
  <tools><allow name="project_backups_operation" /></tools>
  <steps><tool name="project_backups_operation" result="backups"><input name="name" value="{{name}}" /></tool></steps>
  <exit mode="copy">Return retained backup IDs unchanged. No execution or changes occurred.</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>name
Requires a supplied value.
Writing example ↗
04
<systemPrompt>
Sets the child's instructions.
Writing example ↗
05
<tools>
Defines available capabilities.
Writing example ↗
06
<allow>project_backups_operation
Grants an existing tool.
Writing example ↗
07
<steps>
Orders the chat turns.
Writing example ↗
08
<tool>project_backups_operation
Executes a declared host operation.
Writing example ↗
09
<input>name
Binds a named operation or child input.
Writing example ↗
10
<exit>
Returns the output unchanged.
Writing example ↗

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