update

src/type.jl

@@ -177,7 +177,7 @@ function sommelier(
         Dict(
           "role" => "system",
           "content" => [
-            Dict("type" => "text", "text" => "You are a helpful assiatant"),
+            Dict("type" => "text", "text" => "You are a helpful assistant"),
           ]
         ),
         Dict(
@@ -197,10 +197,8 @@ function sommelier(
       ]
   """
   memory = Dict{String, Any}(
-            "shortmem"=> OrderedDict{String, Any}(
-              "db_search_result"=> Any[],
-              "scratchpad"=> "",
-            ),
+            "shortmem"=> OrderedDict{String, Any}(),
+            "scratchpad"=> "",
             "events"=> Vector{Dict{String, Any}}(),
             "state"=> Dict{String, Any}(
             ),
@@ -237,6 +235,7 @@ function sommelier(
     </Store_policy>
     <Store_guidelines>
       - Greeting the customer warmly by ask them how could you help. Do not ask any other questions during this greeting.
+      - Customer may provide images for you to look up.
       - Encourage the customer to explore different options and try new things.
       - If you are unable to locate the desired item in the database after 2 attempts, it may not be available in your inventory. In such cases, inform the user that the item is unavailable and suggest an alternative instead.
       - Your store carries only wine.
@@ -250,10 +249,10 @@ function sommelier(
           Example query 2: "Red or white wine, medium tannin, price under 700 USD"
           Example query 3: "white wine, region: Tuscany or Bordeaux, country: Italy or France
       - PRESENTBOX which you can use to to generate proper dialogue to present wines you have found in your inventory to the user. The input are wine names that you want to present. The output is presentation of the wines.
-      - ENDCONVERSATION which you can use to generates a natural dialogue to gracefully close the conversation with the user. The input is "nothing" keyword. The output is a natural, context-aware dialogue extension that smoothly concludes the conversation.
+      - ENDCONVERGUIDELINE which you can use to check the store guidelines about how to end the conversation with the user. The input is "nothing" keyword. The output is the guidelines that you can follow.
     </Available tools>
     <your role>
-      Your name is $(newAgent.name). You are a sommelier for website-based $(newAgent.retailername)'s wine store. You are working under your mentor supervision.
+      Your name is $(newAgent.name). You are a helpful sommelier for website-based $(newAgent.retailername)'s wine store. You are working under your mentor supervision.
     </your role>
     <situation>
      Your customer is coming into the store
@@ -272,19 +271,17 @@ function sommelier(
       2) Processing sales orders or engaging in any other sales-related activities. These are the job of our sales team at the store.
       3) Answering questions or offering additional services beyond those related to your store's wine recommendations such as discounts, quantity, rewards programs, promotions, delivery options, shipping, boxes, gift wrapping, packaging, personalized messages or something similar. These are the job of our sales team at the store.
     </your responsibility does NOT includes>
-    <at each round of conversation, you will be given the following information>
-      context: additional information about the current situation
-    </at each round of conversation, you will be given the following information>
     <you should then respond to the user with interleaving Plan, Action_name, Action_input>
       1) plan: Based on the current situation, state a complete action plan to complete the task. Be specific.
-      2) actionname: (Typically corresponds to the execution of the first step in your plan) Can be one of the available tool name
-      3) actioninput: The input to the action you are about to perform according to your plan.
+      2) action_name: (Typically corresponds to the execution of the first step in your plan) Can be one of the available tool name
+      3) action_input: The input to the action you are about to perform according to your plan.
+      After the tool is executed you gets "action_result". It is the output from the tool you selected.
     </you should then respond to the user with interleaving Plan, Action_name, Action_input>
     <you should only respond in JSON format as described below>
     {
       "plan": "...",
-      "actionname": "...",
-      "actioninput": "..."
+      "action_name": "...",
+      "action_input": "..."
     }
     </you should only respond in format as described below>