|
47 | 47 | title: "The subject of this conversation is %{topic_title}"
|
48 | 48 | first_post: "The first thing someone said was %{username} who said %{raw}"
|
49 | 49 | post: "%{username} said %{raw}"
|
| 50 | + function: |
| 51 | + calculator: |
| 52 | + description: | |
| 53 | + Useful for getting the result of a math expression. It is a general purpose calculator. It works with Ruby expressions. |
| 54 | +
|
| 55 | + You can retrieve the current date from it too and using the core Ruby Time method to calculate dates. |
| 56 | +
|
| 57 | + The input to this tool should be a valid mathematical expression that could be executed by the base Ruby programming language with no extensions. |
| 58 | +
|
| 59 | + Be certain to prefix any functions with 'Math.' |
| 60 | +
|
| 61 | + Usage: |
| 62 | + Action Input: 1 + 1 |
| 63 | + Action Input: 3 * 2 / 4 |
| 64 | + Action Input: 9 - 7 |
| 65 | + Action Input: Time.now - 2 * 24 * 60 * 60 |
| 66 | + Action Input: Math.cbrt(13) + Math.cbrt(12) |
| 67 | + Action Input: Math.sqrt(8) |
| 68 | + Action Input: (4.1 + 2.3) / (2.0 - 5.6) * 3 |
| 69 | + parameters: |
| 70 | + input: the mathematical expression you need to process and get the answer to. Make sure it is Ruby compatible. |
| 71 | + error: "'%{parameter}' is an invalid mathematical expression, make sure if you are trying to calculate dates use Ruby Time class" |
| 72 | + forum_search: |
| 73 | + description: | |
| 74 | + Search the local forum for information that may help you answer the question. Especially useful when the forum specialises in the subject matter of the query. |
| 75 | + Searching the local forum is preferable to searching google or the internet and should be considered higher priority. It is quicker and cheaper. |
| 76 | +
|
| 77 | + Input should be a search query. You can optionally also specify the number of posts you wish returned from your query. |
| 78 | +
|
| 79 | + Outputs text from the Post and a url link to it you can provide the user. When presenting the url in your reply, do not embed in an anchor, just write the straight link. |
| 80 | + parameters: |
| 81 | + query: "search query for looking up information on the forum" |
| 82 | + number_of_posts: "specify the number of posts you want returned from your query" |
| 83 | + answer_summary: "The top %{number_of_posts} posts on the forum related to this query are, best match first:\n\n" |
| 84 | + answer: "Number %{rank}: the post is at this web address: %{url}, it was written by '%{username}' on %{date} and the text is '%{raw}'.\n\n" |
| 85 | + error: "'%{query}': my search for this on the forum failed." |
| 86 | + google_search: |
| 87 | + description: | |
| 88 | + A wrapper around Google Search. |
| 89 | +
|
| 90 | + Useful for when you need to answer questions about current events. |
| 91 | + Always one of the first options when you need to find information on internet. |
| 92 | +
|
| 93 | + Input should be a search query. |
| 94 | + parameters: |
| 95 | + query: "search query for looking up information on the internet" |
| 96 | + error: "%{query}: my search for this on the internet failed." |
| 97 | + news: |
| 98 | + description: | |
| 99 | + A wrapper around the News API. |
| 100 | +
|
| 101 | + Useful for when you need to answer questions about current events in the news, current events or affairs. |
| 102 | +
|
| 103 | + Input should be a search query and a date from which to search news, so if the request is today, the search should be for todays date |
| 104 | + parameters: |
| 105 | + query: "query string for searching current news and events" |
| 106 | + start_date: "start date from which to search for news in format YYYY-MM-DD" |
| 107 | + answer: "The latest news about this is: " |
| 108 | + error: "ERROR: Had trouble retrieving the news!" |
| 109 | + stock_data: |
| 110 | + description: | |
| 111 | + An API for MarketStack stock data. You need to call it using the stock ticker. You can optionally also provide a specific date. |
| 112 | + parameters: |
| 113 | + ticker: "ticker for share or stock query" |
| 114 | + date: "date for data in format YYYY-MM-DD" |
| 115 | + answer: "Ticker %{ticker} had a day close of %{close} on %{date}, with a high of %{high} and a low of %{low}" |
| 116 | + error: "ERROR: Had trouble retrieving information from Market Stack for stock market information!" |
| 117 | + wikipedia: |
| 118 | + description: | |
| 119 | + A wrapper around Wikipedia. |
| 120 | +
|
| 121 | + Useful for when you need to answer general questions about |
| 122 | + people, places, companies, facts, historical events, or other subjects. |
| 123 | +
|
| 124 | + Input should be a search query |
| 125 | + parameters: |
| 126 | + query: "query string for wikipedia search" |
| 127 | + answer: "The relevant wikipedia page has the following summary: '%{summary}' and the article can be found at this url link: %{url}" |
| 128 | + error: "ERROR: Had trouble retrieving information from Wikipedia!" |
| 129 | + agent: |
| 130 | + handle_function_call: |
| 131 | + answer: "The answer is %{result}." |
| 132 | + call_function: |
| 133 | + error: "There was something wrong with your function arguments" |
| 134 | + final_thought_answer: |
| 135 | + opener: "To answer the question I will use these step by step instructions.\n\n" |
| 136 | + thought_declaration: "I will use the %{function_name} function to calculate the answer with arguments %{arguments}.\n\n" |
| 137 | + final_thought: "%{thoughts} Based on the above, I will now answer the question, this message will only be seen by me so answer with the assumption with that the user has not seen this message." |
| 138 | + |
50 | 139 | errors:
|
51 | 140 | general: "Sorry, I'm not well right now. Lets talk some other time. Meanwhile, please ask the admin to check the logs, thank you!"
|
52 | 141 | retries: "I've tried working out a response for you several times, but ultimately failed. Please contact the admin if this persists, thank you!"
|
|
0 commit comments