Current Date and Time

What it is

Native tool that returns the current date and time already in the configured timezone (defaults to America/Sao_Paulo) when the agent needs to know “what day/hour is now”.

Language models don’t have real notion of present time — they know up to a training cutoff. Without this tool, the agent may invent the date or use a stale reference.

The result comes back in the local time of the chosen timezone, with the weekday included. The agent uses that value directly to reason about business hours, working days, and deadlines — no timezone conversion needed, which is exactly where models tend to make mistakes.

When to use

• Scheduling: agent that books meetings, creates reminders, or calculates deadlines.
• Support that needs to say “today”, “tomorrow”, “last week” accurately.
• Business-hours decisions: handing off to a human only during working hours, for example.
• Responses involving promotions with expiration date, coupon validity, return deadlines.
• Contextual greetings (“good morning”, “good evening”) based on the local hour.

Configuration

1. In the agent’s Tools tab, click + Add Tool.
2. Under NATIVE TOOLS, pick Current Date and Time.
3. Click the tool to open its options and choose your business Timezone (the selector shows a “Now in this timezone” preview so you can double-check). The default is America/Sao_Paulo.
4. Save.

The timezone defines the local time the agent reads as “now” — so set it to your business’s timezone, especially if you use business-hours rules in the prompt.

How the agent invokes

The agent decides to call this tool when the question or task depends on the current moment:

• “what day is today?”
• “what’s the deadline if delivery is in 5 business days?”
• “is this coupon still valid?”
• “are you open right now?”
• “set a reminder for tomorrow morning”

The result carries the time already in the configured timezone (date, local time, and weekday). The agent uses that value directly, without mentioning timezone or doing any conversion.

Limitations and notes

• One timezone per agent. The tool uses the configured timezone, not each user’s own timezone. To personalize per user (e.g., “good evening” in their tz), store the timezone in a conversation note or in the profile and guide the agent to use it.
• Write times in local time. Since the time already comes back local, write the prompt’s windows in natural local time (e.g., “from 9am to 5pm”) — don’t compensate the timezone manually.
• No extra cost. The call is cheap and fast — returns in milliseconds.
• Watch out for date arithmetic. The model isn’t perfect at calendar math (business days, holidays). For critical cases, validate on your application side.