System prompt
The system prompt for agentic functions is defined in terms of templating variables, shown below.System
User prompt
The user prompt for agentic functions is defined in terms of templating variables, shown below.User
Templating variables
STARTER
Initial context defining the agent’s role and the function being executed.Note:
function_description: The doc-string provided for the agentic function.function_name: The name of the agentic function.function_stub: Formatted stub of the agentic function.
STARTER
OBJECTIVES
Core constraints defining available resources, code execution rules, and output requirements.Note:
is_returning_text:Trueif the return type of the agentic function isstr/string,Falseotherwise.available_modules: A list of the names of all available modules in the RPEL.is_python_sdk:Trueif request made from the Python SDK,Falseotherwise.has_global_resources:Trueif resources provided viascopein the decorator,Falseotherwise.global_resources_stub: Formatted stubs of all defined resources provided viascopein the decorator.
OBJECTIVES
WORKFLOW
Step-by-step process for analyzing inputs, executing code, and producing results.
WORKFLOW
INTERACTIONS
Defines the two types of messages the agent receives during execution.
INTERACTIONS
OUTPUT
Formatting rules for agent responses and code blocks.
OUTPUT
NOTES
Key behavioral guidelines for handling tasks, return types, and error conditions.
NOTES
USER_PROMPT
Formatted task description, expected return type, and additional tools.Note:
task: Thetaskprovded on calling the agent.return_type: Formatted expected return type for the agent’s task.has_local_resources:Trueif the agentic function takes in arguments,Falseotherwise.local_resources_stub: Formatted stubs of all arguments on calling the agentic function.
USER_PROMPT
RETURN_TYPE
Formatted expected return type for the agent’s task.
STUBS
Formatted stubs for all defined resources available to the agent.