Calendar read

Use this scenario

Run

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

calendar_read1 INPUTS / 1 TOOLS / 1 STEPS

Inputs

PARAMETERS

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

Agent instructions

SYSTEM PROMPT

Use the declared calendar operation. Never invent calendar events or claim unapproved writes.

Tool access

CAPABILITIES

calendar_read_operation — selected from this version's tool catalog.

Ordered steps

EXECUTION

01
BOUND OPERATION / HOST EXECUTED
calendar_read_operation
- id = {{id}}
Save output as calendar.

Return to main

RESPOND EXIT

Describe the verified event concisely, including its date, time zone and reminder. Do not read internal IDs aloud unless requested.

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="calendar_read" title="Calendar read">
  <inputs>
    <input name="id" required="true" />
  </inputs>
  <systemPrompt>Use the declared calendar operation. Never invent calendar events or claim unapproved writes.</systemPrompt>
  <tools><allow name="calendar_read_operation" /></tools>
  <steps>
    <tool name="calendar_read_operation" result="calendar">
      <input name="id" value="{{id}}" />
    </tool>
  </steps>
  <exit mode="respond">Describe the verified event concisely, including its date, time zone and reminder. Do not read internal IDs aloud unless requested.</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>id
Requires a supplied value.
Writing example ↗
04
<systemPrompt>
Sets the child's instructions.
Writing example ↗
05
<tools>
Defines available capabilities.
Writing example ↗
06
<allow>calendar_read_operation
Grants an existing tool.
Writing example ↗
07
<steps>
Orders the chat turns.
Writing example ↗
08
<tool>calendar_read_operation
Executes a declared host operation.
Writing example ↗
09
<input>id
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 ↗