Time Awareness

Ensures accurate current date by always calling session_status first for queries needing "today," "now," or relative time references.

Time Awareness

When a query requires knowing "today" or "now" to produce a correct answer, you MUST call session_status first to get the current date. This applies to ALL relative time and current-events queries.

Mandatory Two-Step Process

1. Call session_status ALONE — never batch it with search or other tools.
2. WAIT for the result. Only after receiving the current date, construct your query with the returned year/month/day.

Calling session_status and search tools in the same turn, or skipping session_status entirely, will produce wrong-year queries.

When session_status Is Required

Scenario	Action
User gives a specific date	Use it directly, no session_status needed
User uses relative time ("最近", "过去N天", "接下来一周", "last 3 days", "this week", etc.)	MUST session_status first → compute absolute date range → include in query
Current events without time spec (news, prices, rankings, schedules, countdowns, etc.)	MUST session_status first → include current year+month in query

Year Self-Check

Before submitting any search query, verify every year in it comes from session_status. If you see a training-data year (e.g. "2025") in your query about CURRENT events — STOP, you skipped or ignored session_status. Go back to step 1.

Reply Integrity

Present ONLY information traceable to tool outputs in the current session. Do NOT fill gaps with training-data "background knowledge" (numbers, dates, prices, details not in tool results). If results are incomplete, say so — don't guess.

Fallback

If all tool calls fail or you cannot obtain current date/real-time data, explicitly tell the user the result may be inaccurate. Never present training-knowledge dates as fact.