You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Include course codes when referencing specific courses
247
247
- If information is missing from the context but likely exists, try to use info from web to answer. If still not able to form a decent response, acknowledge the limitation
248
248
- For unrelated questions, politely explain that you're specialized in UTSC academic information
249
+
- Format long lists of timetables as a table
249
250
250
251
## Tool call guidelines
251
252
- Include the timetable ID in all getTimetables tool call responses
252
-
- For every tool call, for each timetable that it gets/deletes/modifies/creates, include a link underneath it displayed as "View timetable" to ${process.env.CLIENT_APP_URL}/dashboard/timetable?edit=[[TIMETABLE_ID]] , where TIMETABLE_ID is the id of the respective timetable.
253
+
- Link: For every tool call, for each timetable that it gets/deletes/modifies/creates, include a link with it displayed as "View Timetable" to ${process.env.CLIENT_APP_URL}/dashboard/timetable?edit=[[TIMETABLE_ID]] , where TIMETABLE_ID is the id of the respective timetable.
253
254
- If the user provides a course code of length 6 like CSCA08, then assume they mean CSCA08H3 (H3 appended)
254
255
- If the user wants to create a timetable, first call getCourses to get course information on the requested courses, then call generateTimetable.
255
-
- For the response to create timetable, format as a table.
- Be concise and direct when answering course-related questions
432
433
- Use bullet points for listing multiple pieces of information
434
+
- Use tables for listing multiple offerings, courses, or other information that could be better viewed in tabular fashion
433
435
- Include course codes when referencing specific courses
434
436
- If information is missing from the context but likely exists, try to use info from web to answer. If still not able to form a decent response, acknowledge the limitation
435
437
- For unrelated questions, politely explain that you're specialized in UTSC academic information
.describe("The type of restriction being applied"),
73
+
.describe(
74
+
"The type of restriction being applied. Restrict before restricts all times before 'endTime', Restrict Before restricts all times after 'startTime', Restrict Between restricts all times between 'startTime' and 'endTime', Restrict Day restricts the entirety of each day in field 'days', and Days Off enforces as least 'numDays' days off per week."
75
+
),
74
76
days: z
75
77
.array(DayOfWeekEnum)
76
-
.default(["SU","MO","TU","WE","TH","FR","SA"])
78
+
.default(["MO","TU","WE","TH","FR"])
77
79
.describe("Specific days of the week this restriction applies to"),
78
80
numDays: z
79
81
.number()
80
82
.positive()
81
83
.max(4,"Cannot block all days of the week")
82
84
.optional()
83
85
.describe(
84
-
"If type is Days Off, then this field is used and describes min number of days off per week.",
86
+
"If type is Days Off, then this field is used and describes min number of days off per week. For example, if set to 2, and 'type' is Days Off, then this means we want at least 2 days off per week."
85
87
),
86
88
startTime: z
87
89
.string()
88
90
.optional()
89
91
.describe(
90
-
"If type is Restrict After, or Restrict Between, then this field describes the start time of the restricted time. Formatted HH:mm:ss",
92
+
"If type is Restrict After, or Restrict Between, then this field describes the start time of the restricted time. Formatted HH:mm:ss"
91
93
),
92
94
endTime: z
93
95
.string()
94
96
.optional()
95
97
.describe(
96
-
"If type is Restrict Before, or Restrict Between, then this field describes the end time of the restricted time. Formatted HH:mm:ss",
98
+
"If type is Restrict Before, or Restrict Between, then this field describes the end time of the restricted time. Formatted HH:mm:ss"
0 commit comments