Skip to main content
Glama

tz_convert

Convert an instant or local wall time between IANA time zones, returning UTC offsets, abbreviations and DST gap or overlap handling for up to 20 target zones.

Instructions

IANA time zone conversion: an instant (ISO with offset, Z, or Unix) or a local wall time in a source zone converted to up to 20 zones, with UTC offset, abbreviation and DST gap/overlap handling (ambiguous times return both instants). Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "to": "<to>"
    },
    "name": "tz_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget zones, comma-separated
fromNoSource IANA zone for local times, default UTC
timeNoISO date-time or local time; default now

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses DST gap/overlap handling, that ambiguous times return both instants, the 20-zone cap, the per-successful-call cost, and that a missing payment key yields a 402 challenge. It stops short of describing rate limits or the exact response envelope, but the behavioral profile is substantially richer than typical.

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?

The core conversion behavior is front-loaded in one dense sentence, followed by the payment/error behavior. Every clause earns its place: formats, cap, DST handling, and cost are all decision-relevant, with no filler.

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?

No output schema exists, and the description compensates by naming the returned fields (UTC offset, abbreviation, both instants for ambiguous times). Combined with full parameter documentation and explicit payment behavior, an agent has nearly everything needed; only the precise response shape or error behavior for invalid zones is unstated.

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 the baseline is 3, but the description adds real meaning beyond the schema by specifying accepted time formats (ISO with offset, Z, or Unix), the semantic role of 'from' as only relevant for local wall times, and the 20-zone ceiling on 'to'. Defaults (UTC, now) are covered by the schema itself.

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?

States a specific verb and resource (IANA time zone conversion) plus the exact scope: an instant or local wall time in a source zone converted to up to 20 target zones. An agent can tell immediately this is a zone-conversion utility, distinct from FX or other sibling tools.

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?

The description makes clear what inputs are accepted and mentions payment prerequisites (0.001 USDC on Base, 402 challenge without a key), which implies when the tool is callable. However, it gives no explicit guidance on when to prefer this tool over alternatives or when not to use it; usage context is only implied by the input description.

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