Store data outside LLM context

In this example, we demonstrate how to use set_meta_data to store metadata to reference later. The AI agent, will store a user’s name and then look up any additional stored information.

The benefit of storing information in meta_data is that the information it can be referenced from any function with the same meta_data_token, while also never being exposing the information to the language model. This allows for the AI agent to store sensitive information without the risk of it being exposed to the AI agent.

1. Storing user information

The store_user function is used to store the user’s name. The user’s name and a secret associated with them are stored as meta_data.

1 - function: store_user
2   description: Store the user information
3   parameters:
4     type: object
5     properties:
6       name:
7         type: string
8         description: The name of the user
9   data_map:
10     webhooks:
11       - url: 'https://example.com/name_bank?name=${lc:args.name}'
12         method: GET
13         output:
14           response: The user information was stored. User information can now be looked up with the "get_user_info" function.
15           action:
16             - set_meta_data:
17                 '${lc:input.args.name}: ${Records[0].secret}'
18             - toggle_functions:
19                 - active: true
20                   function: get_user_info
21             - say: Your info was stored.
22   meta_data_token: example_token

This will send a request to data_map.webhooks.url with the user’s name as a query parameter. In this example, we have our server responding with a Records array in the response. This will contain information on the user.

Server Response:

1 {
2   "response": "The user information was stored.",
3   "Records": [{ "secret": ["Info about user here"] }]
4 }

Once the response has returned from the webhook, the meta_data will be set using set_meta_data in the data_map.webhooks.output.action of the function, the get_user_info function will be toggled on using toggle_functions, and the user will be notified that their information was stored.

The meta_data key is set to the users name and the value is set to the first value in the Records array.

1 - set_meta_data:
2     '${lc:input.args.name}: ${Records[0].secret}'

2. Looking up user information

After storing the user information in meta_data, we can now look up the user information with the get_user_info function.

1 - function: get_user_info
2   description: lookup user information
3   parameters:
4     type: object
5     properties:
6       name:
7         type: string
8         description: The name of the user
9   data_map:
10     expressions:
11       - string: '${lc:args.name}'
12         pattern: /\\w+/i
13         output:
14           response: The meta_data is valid.
15           action:
16             - say: 'Your info is ${meta_data.${lc:args.name}}'
17             - stop: true
18       - string: .*
19         pattern: .*
20         output:
21           response: The meta_data is invalid. User has not been told their information.
22   active: false
23   meta_data_token: example_token

This function will check if the meta_data is valid by checking if the user’s name is a key in the meta_data object. If the meta_data is valid, the user will be told their information. If the meta_data is invalid, the user will be told that their information has not been stored.

Full example

1 sections:
2   main:
3     - ai:
4         prompt:
5           text: >-
6             Your name is Mr. Blabbermouth. You help the user.
7             ## Handling The User
8             - You are asked to store a user's information.
9               - You ask for their name.
10             - You use the 'store_user' function to store the users name.
11             ### Looking up user information
12             - You can only look up a users information after storing it.
13         post_prompt:
14           text: Summarize the call in JSON format.
15           temperature: 0.1
16           top_p: 0.1
17         post_prompt_url: https://example.com/post_prompt_url
18         params:
19           swaig_allow_swml: true
20         SWAIG:
21           functions:
22             - function: store_user
23               description: Store the user information
24               parameters:
25                 type: object
26                 properties:
27                   name:
28                     type: string
29                     description: The name of the user
30               data_map:
31                 webhooks:
32                   - url: 'https://example/name_bank?name=${lc:args.name}'
33                     method: GET
34                     output:
35                       response: The user information was stored. User information can now
36                         be looked up with the "get_user_info" function.
37                       action:
38                         - set_meta_data:
39                             '${lc:input.args.name}: ${Records[0].secret}'
40                         - toggle_functions:
41                             - active: true
42                               function: get_user_info
43                         - say: Your info was stored.
44               meta_data_token: example_token
45             - function: get_user_info
46               description: lookup user information
47               parameters:
48                 type: object
49                 properties:
50                   name:
51                     type: string
52                     description: The name of the user
53               data_map:
54                 expressions:
55                   - string: '${lc:args.name}'
56                     pattern: /\w+/i
57                     output:
58                       response: The meta_data is valid. User has already been told their
59                         information. Do no repeat it.
60                       action:
61                         - say: 'Your info is ${meta_data.${lc:args.name}}'
62                         - stop: true
63                   - string: /.*/
64                     pattern: /.*/
65                     output:
66                       response: The meta_data is invalid. User has not been told their information.
67               active: "false"
68               meta_data_token: example_token