Skip to main content
Glama

worldtime_by_timezone

Read-onlyIdempotent

Retrieve the current local time for a specified IANA timezone to coordinate schedules and workflows across regions.

Instructions

Get current time for a specific timezone.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "timezone": "<timezone>"
    },
    "name": "worldtime_by_timezone"
  }
}

Input Schema

NameRequiredDescriptionDefault
timezoneYesIANA timezone, e.g. 'America/New_York', 'Europe/London'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds no behavior beyond the core purpose (no auth needs, rate limits, or return-shape hints), so it does not enrich the annotation-provided context.

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?

A single front-loaded sentence with zero waste; there is nothing to trim.

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

Completeness3/5

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

For a trivial read tool the annotations and full-coverage schema carry most of the load, but with no output schema the description could usefully state what is returned (e.g., offset, DST status, formatted time). As written it leaves return semantics unspecified.

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

Parameters3/5

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

The single parameter has 100% schema coverage with an IANA example, so the schema does the work. The description adds no syntax or formatting detail beyond what the schema already specifies, making 3 the correct baseline.

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

Purpose4/5

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

Specific verb ('Get') plus resource ('current time') and scope ('for a specific timezone') make the function unambiguous. However, it does not differentiate itself from close siblings like time_api_current_by_zone, worldtime_by_ip, or datetime_current_time, so an agent must infer which to pick.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus the many other timezone/time tools in the catalog. No prerequisites, exclusions, or alternative routing are provided.

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

Deploy Server

Other Tools