Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

time_world_clock

Read-only

Display current wall-clock time across multiple IANA time zones simultaneously, with date, UTC offset, abbreviation, weekday, and DST status. Use snapshot mode for live or pinned instants, or list supported timezones.

Instructions

World Clock. Render the current wall-clock time across multiple IANA time zones at once, each with date, UTC offset, zone abbreviation, weekday, and DST flag. The 'operation' field selects the mode. 'snapshot' takes 'tzs' (1-12 IANA names) and an optional 'iso' instant; when 'iso' is omitted it uses the server's current time, so the result changes every call (live clock). Pass an explicit 'iso' to pin a fixed instant and get a stable, repeatable result. 'listSupportedTimezones' returns the curated IANA name list and ignores other fields. Use this for a multi-city now view; use time_timezone_converter for one-off wall-clock zone-to-zone conversion, or time_iso_8601_formatter for ISO/RFC string parsing. Pure local computation against the bundled tz database, no network or storage; read-only, non-destructive, rate-limited (60 req/min anonymous, no auth). Each zone reports isoLocal, weekday, offset, abbreviation, and isDst.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesMode to run. 'snapshot' renders the instant across the 'tzs' zones. 'listSupportedTimezones' returns the curated IANA list and ignores all other fields.
tzsNoIANA time zone names to render, 1-12 entries such as America/New_York or Asia/Tokyo. Required for snapshot.
isoNoOptional ISO 8601 instant to render. When omitted or empty the server current time is used, making the result non-idempotent. Supply it to pin a fixed instant.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoThe operation that was run, echoed back.
dataNoResult payload; an object for snapshot, a string array for listSupportedTimezones.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Description adds significant behavioral context beyond annotations: pure local computation, no network/storage, rate-limited (60 req/min anonymous), and explains live vs pinned instant behavior. Annotations already declare readOnlyHint and destructiveHint, but description enriches understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise yet comprehensive, front-loaded with purpose, then operational details. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists and annotations are rich, the description is complete. It covers all operations, parameter behaviors, and use cases. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds meaning: explains operation modes, tzs constraints (1-12 entries), and iso's optional nature with idempotency implications. This goes beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool renders wall-clock time across multiple IANA time zones with details like date, offset, abbreviation, etc. It distinguishes itself from sibling tools like time_timezone_converter and time_iso_8601_formatter, making its purpose specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance is provided: 'Use this for a multi-city now view; use time_timezone_converter for one-off wall-clock zone-to-zone conversion, or time_iso_8601_formatter for ISO/RFC string parsing.' Also explains operation modes and when to use each.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server