Kanium-PUBLIC/KaniumCogs
5
0
Fork 0
Code Issues 6 Pull Requests Packages Projects 1 Releases Wiki Activity

Enhance Weather Function with Dynamic Date Awareness & Clarification Prompts #2

New Issue
Closed
opened 2025-06-14 14:42:56 +02:00 by AllfatherHatt · 2 comments
AllfatherHatt commented 2025-06-14 14:42:56 +02:00
Owner
Copy Link

User Story

As a user, I want the weather command to always know today’s date and to ask me for any missing details (date or location) so that the forecast is accurate and doesn’t break.

Description

  • Inject (for example) an ISO-8601 timestamp into every weather function call.
  • Detect when date or location is omitted or ambiguous, and prompt the user:
    “Sure—what city (and which date) would you like the forecast for?”
  • Only call the weather API once all required parameters are provided.

Acceptance Criteria

  1. The weather function schema includes a timestamp field set to the current UTC time.
  2. If date or location is missing, the bot asks a follow-up question before proceeding.

Definition of Done

  • Code reviewed, demo'ed & accepted before merge
  • Code merged
  • Docs updated
# User Story As a user, I want the weather command to always know today’s date and to ask me for any missing details (date or location) so that the forecast is accurate and doesn’t break. ## Description * Inject (for example) an ISO-8601 timestamp into every weather function call. * Detect when date or location is omitted or ambiguous, and prompt the user: “Sure—what city (and which date) would you like the forecast for?” * Only call the weather API once all required parameters are provided. ## Acceptance Criteria 1. The weather function schema includes a timestamp field set to the current UTC time. 2. If date or location is missing, the bot asks a follow-up question before proceeding. ## Definition of Done - [x] Code reviewed, demo'ed & accepted before merge - [x] Code merged - [x] Docs updated
AllfatherHatt added this to the Reginald Camp project 2025-06-14 15:43:57 +02:00
T-BENZIN commented 2025-06-16 06:19:01 +02:00
Owner
Copy Link

Most oblivious solution to me is to handle date inside of the tool function the way Reginald works with the best, then process it into the whatever format Weather API uses.

Most oblivious solution to me is to handle date inside of the tool function the way Reginald works with the best, then process it into the whatever format Weather API uses.
T-BENZIN moved this to In Progress in Reginald Camp on 2025-06-17 07:11:32 +02:00
T-BENZIN added a new dependency 2025-06-17 08:16:15 +02:00
#8 Made improvements in AI Agent's tool get_forecast_weather
T-BENZIN removed a dependency 2025-06-17 08:16:42 +02:00
#8 Made improvements in AI Agent's tool get_forecast_weather
T-BENZIN added a new dependency 2025-06-17 08:16:50 +02:00
#8 Made improvements in AI Agent's tool get_forecast_weather
T-BENZIN commented 2025-06-18 17:13:15 +02:00
Owner
Copy Link

Weather forecast logic updated

Weather forecast logic updated
AllfatherHatt moved this to Done in Reginald Camp on 2025-06-18 17:14:15 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project Reginald Camp
Assignees
Clear assignees
AllfatherHatt T-BENZIN
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Blocks
#8 Made improvements in AI Agent's tool get_forecast_weather
Kanium-PUBLIC/KaniumCogs
Reference: Kanium-PUBLIC/KaniumCogs#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?