Get the current local time in an IANA timezone, including the UTC offset, zone abbreviation and whether DST is in effect. Use whenever you need to know what time it is 'now' somewhere.
| Name | Required | Description | Default |
|---|---|---|---|
| timezone | Yes | IANA timezone, e.g. 'Europe/Madrid', 'Asia/Kolkata'. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided. The description discloses that the tool returns the current time, UTC offset, zone abbreviation, and DST status. For a simple read-only lookup tool, this adequately describes behavior without missing critical details like side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description consists of two short sentences. The first sentence states the tool's operation and outputs, and the second provides usage context. No superfluous words, well-structured and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple tool with one parameter and no output schema, the description covers the return values (time, offset, abbreviation, DST) adequately. The tool's functionality is fully communicated without gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage with a single parameter described as 'IANA timezone, e.g. 'Europe/Madrid''. The description does not add extra semantics beyond the schema's description. With high schema coverage, baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns current local time in an IANA timezone, including UTC offset, zone abbreviation, and DST status. This is specific and distinguishes it from sibling tools like 'convert_timezone' or 'list_timezones' which handle different time operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states 'Use whenever you need to know what time it is 'now' somewhere.' This provides clear context for when to use the tool. No explicit when-not or alternatives are given, but the guidance is sufficient given the tool's simplicity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: conversion (single and batch), arithmetic, meeting scheduling, holiday checking, timezone lookup, current time, and offset. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., convert_batch, list_timezones, is_holiday). Minor variations like 'now_in' and 'tz_offset' still adhere to the pattern.
Nine tools is ideal for a timezone toolkit. Each tool serves a distinct and necessary function without being excessive or insufficient for the domain's scope.
The toolset covers all major timezone operations: conversion, arithmetic, current time, offset, discovery, holidays, and meeting slot calculation. No obvious gaps for common use cases.