Skip to main content
Glama

Convert a local time between IANA time zones

timezone
Read-only

The current time in an IANA time zone (its UTC offset and whether DST applies) and, with time and to, the conversion of a local time from one zone to another. Computed in the Worker with the runtime's time zone data; no outside call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "zone": "<zone>"
    },
    "name": "timezone"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoTarget IANA zone for the conversion
timeNoLocal time to convert, e.g. 2026-03-29T01:30
zoneYesIANA zone, e.g. Europe/Istanbul

Output Schema

NameRequiredDescriptionDefault
nowNo
zoneNo
sourceNo
checkedAtNo
conversionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the pricing model ($0.002 per successful call), the payment rail (x402 with USDC on Base, Solana and 10+ networks), and that failed calls are free — all operationally important for an agent to know before calling. It also states computation happens in the Worker with runtime time-zone data and involves no outside request; that sits in mild tension with openWorldHint=true, but plausibly reads as 'no third-party HTTP API' rather than a true contradiction. Error behavior for bad zones is not covered.

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

Conciseness3/5

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

Purpose is front-loaded and there is no filler, but roughly half the text is commercial detail (price, payment networks, failed-call policy) and the opening sentence is grammatically tangled enough to require re-reading. It is efficient in content but weaker in structure and parseability.

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

Completeness4/5

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

With only 3 fully documented parameters, an output schema, and read-only annotations, the description covers everything an agent needs in order to call it: what each mode does, where computation happens, and what it costs. The only real gap is failure/edge behavior (invalid zone, DST-ambiguous local times), which for a conversion tool of this complexity is a minor omission.

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 a baseline of 3 applies, and the description earns above that by explaining the coupling: 'time' and 'to' together activate conversion, whereas 'zone' alone returns the current time. That conditional relationship is genuinely new meaning not obvious from three flat properties. It does not restate formats, which the schema already handles.

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?

The description names a specific resource (IANA time zone) and two concrete behaviors: returning the current time with UTC offset/DST status, and converting a local time between zones. The elliptical first sentence ('The current time in an IANA time zone ... and, with time and to, the conversion of ...') lacks a main verb, which costs a bit of immediate readability. It is still far more specific than a tautology and no sibling overlaps in scope.

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

Usage Guidelines3/5

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

It gives conditional usage ('with time and to, the conversion...'), so an agent knows the conversion mode is parameter-triggered rather than a separate tool. There is no explicit when-not-to-use, no mention of how to handle invalid zones, and no routing to any alternative despite a large sibling catalog. Usage is implied rather than guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources