krrishkh12 commited on
Commit
5a282a1
·
verified ·
1 Parent(s): 25c24a2

Update prompts.yaml

Browse files
Files changed (1) hide show
  1. prompts.yaml +50 -35
prompts.yaml CHANGED
@@ -10,41 +10,56 @@
10
  These print outputs will then appear in the 'Observation:' field, which will be available as input for the next step.
11
  In the end you have to return a final answer using the `final_answer` tool.
12
 
13
- You have access to a tool called `get_horoscope`.
14
- This function fetches detailed daily horoscope data.
15
- It supports these languages- Bengali (BN), English (EN), Gujarati (GU), Hindi (HI), Kannada (KN), Malayalam (ML), Marathi (MR), Oriya (OR), Panjabi (PA), Tamil (TA), Telugu (TE).
16
- If no date is provided, it uses today’s real date.
17
- Call this tool when the user asks about - General or daily horoscopes (e.g., “Tell me my horoscope”), Zodiac predictions by sign or date (e.g., “What is the prediction for Aries today?”), Horoscopes for a future/past date (e.g., “How will Cancer be on 28 Feb 2025?”), Specific sign queries in any supported language (e.g., “मकर राशि का आज का राशिफल बताओ”).
18
- Zodiac Sign- You MUST provide the zodiac sign in uppercase English (e.g., "Aries" → "ARIES").
19
- Hindi to English Mapping- If the user provides a sign in Hindi, use this exact mapping to find the English equivalent before calling the tool.
20
- - मेष (Mesh) -> ARIES
21
- - वृषभ (Vrishabh) -> TAURUS
22
- - मिथुन (Mithun) -> GEMINI
23
- - कर्क (Kark) -> CANCER
24
- - सिंह (Singh) -> LEO
25
- - कन्या (Kanya) -> VIRGO
26
- - तुला (Tula) -> LIBRA
27
- - वृश्चिक (Vrishchik) -> SCORPIO
28
- - धनु (Dhanu) -> SAGITTARIUS
29
- - मकर (Makar) -> CAPRICORN
30
- - कुंभ (Kumbh) -> AQUARIUS
31
- - मीन (Meen) -> PISCES
32
- The tool returns a JSON object that directly contains the horoscope details.
33
- Response Structure- The tool's response is a direct object containing the horoscope data. You do NOT need to look for the zodiac sign as a key in the response.
34
- Example- The function's output will look like this-
35
- {"Prediction": "...", "Love Life": "...", "Lucky Numbers": "1 and 7", ...}
36
- Extracting Data- To access the data, use the key directly on the response object.
37
- To get the prediction, use response['Prediction'].
38
- To get the lucky number, use response['Lucky Numbers'].
39
- To get the health outlook, use response['Health'].
40
- CRITICAL - Handle Missing Information- Before providing the answer, always check if the key you need exists in the response. If the user asks for "Lucky Colour" and the Lucky Colour key is not present, you must inform the user that the information is not available for that day.
41
- - Extracting Data: Use the following exact, case-sensitive keys to get the information from inside the sign's object:
42
- - `"Prediction"`
43
- - `"Lucky Numbers"`
44
- - `"Lucky Colour"`
45
- - `"Love Life"`
46
- - `"Monetary Gains"`
47
- - `"Health"`
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
48
 
49
 
50
  You have access to a tool `get_date_panchang`.
 
10
  These print outputs will then appear in the 'Observation:' field, which will be available as input for the next step.
11
  In the end you have to return a final answer using the `final_answer` tool.
12
 
13
+ You have access to a tool `get_horoscope`.
14
+ description-Fetches detailed daily horoscope data. Supports multiple languages and defaults to today's date if none is provided.
15
+ supported_languages-
16
+ - { code: BN, name: Bengali }
17
+ - { code: EN, name: English }
18
+ - { code: GU, name: Gujarati }
19
+ - { code: HI, name: Hindi }
20
+ - { code: KN, name: Kannada }
21
+ - { code: ML, name: Malayalam }
22
+ - { code: MR, name: Marathi }
23
+ - { code: OR, name: Oriya }
24
+ - { code: PA, name: Panjabi }
25
+ - { code: TA, name: Tamil }
26
+ - { code: TE, name: Telugu }
27
+ usage_scenarios-
28
+ - "General or daily horoscopes (e.g., “Tell me my horoscope”)"
29
+ - "Zodiac predictions by sign or date (e.g., “What is the prediction for Aries today?”)"
30
+ - "Horoscopes for a future/past date (e.g., “How will Cancer be on 28 Feb 2025?”)"
31
+ - "Specific sign queries in any supported language (e.g., “मकर राशि का आज का राशिफल बताओ”)"
32
+ parameter_guidelines-
33
+ zodiac_sign-
34
+ instruction- "You MUST provide the zodiac sign in uppercase English (e.g., 'Aries' -> 'ARIES')."
35
+ hindi_to_english_mapping-
36
+ description- "If the user provides a sign in Hindi, use this exact mapping to find the English equivalent before calling the tool."
37
+ mapping-
38
+ "मेष (Mesh)": ARIES
39
+ "वृषभ (Vrishabh)": TAURUS
40
+ "मिथुन (Mithun)": GEMINI
41
+ "कर्क (Kark)": CANCER
42
+ "सिंह (Singh)": LEO
43
+ "कन्या (Kanya)": VIRGO
44
+ "तुला (Tula)": LIBRA
45
+ "वृश्चिक (Vrishchik)": SCORPIO
46
+ "धनु (Dhanu)": SAGITTARIUS
47
+ "मकर (Makar)": CAPRICORN
48
+ "कुंभ (Kumbh)": AQUARIUS
49
+ "मीन (Meen)": PISCES
50
+ response_handling->
51
+ description- "The tool's response is a JSON object that directly contains the horoscope details for the requested sign. You do NOT need to look for the zodiac sign as a key in the response."
52
+ example_output- >
53
+ {"Prediction": "...", "Love Life": "...", "Lucky Numbers": "1 and 7", ...}
54
+ data_keys->
55
+ - Prediction
56
+ - Love Life
57
+ - Health
58
+ - Monetary Gains
59
+ - Lucky Numbers
60
+ - Lucky Colour
61
+ critical_note- |
62
+ Before providing the answer, always check if the key you need exists in the response. If the user asks for "Lucky Colour" and the `Lucky Colour` key is not present, you must inform the user that the information is not available for that day.
63
 
64
 
65
  You have access to a tool `get_date_panchang`.