Skip to main content
Glama

x420_time_zone-convert

Convert an instant or wall-clock time between IANA time zones with DST handled, returning ISO strings with offsets and abbreviations.

Instructions

Time zone converter: Converts an instant or wall-clock time between IANA time zones with DST handled, returning ISO strings with offsets and abbreviations. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.01 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: utc, epoch_ms, from, to (iso, zone, abbreviation, utc_offset) - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"time":"2026-11-19T15:00:00Z","to_tz":"America/Chicago"}.

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_tz": "<to_tz>"
    },
    "name": "x420_time_zone-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoISO 8601, epoch seconds/ms, or 'now' (default now)
to_tzYesIANA zone to convert into, e.g. America/Chicago
from_tzNoIANA zone of a wall-clock time without offset (default UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior4/5

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

The description goes well beyond the annotations: it discloses that the call costs $0.01 USDC settled on Base via x402 from a wallet key, that it is real money, and that the response includes a signed receipt and settlement transaction. That explains why readOnlyHint=false despite a pure conversion semantics, so there is no contradiction. It stops short of describing failure/refund behavior when settlement fails.

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

Conciseness4/5

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

The purpose is front-loaded in the first clause, followed by payment, return shape, and an example in a sensible order. The legal/medical/tax disclaimer sentence is boilerplate that does not help an agent decide or call correctly, which is the only real waste.

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 no output schema, the description usefully enumerates the returned JSON fields (utc, epoch_ms, from/to with iso, zone, abbreviation, utc_offset) plus receipt and settlement data, and it covers cost and auth prerequisites. Minor gaps remain around behavior for ambiguous or nonexistent wall-clock times during DST transitions.

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?

Schema description coverage is 100%, so the schema already documents time (ISO/epoch/'now'), to_tz, and from_tz. The description's example input adds a concrete usage pattern and the 'instant vs wall-clock' phrasing reinforces when from_tz is needed, but it does not add format or edge-case detail beyond the schema, so the baseline of 3 applies.

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 ('Converts an instant or wall-clock time between IANA time zones') and adds the key qualifier that DST is handled. This distinguishes it cleanly from neighbors like x420_currency_convert and x420_units_convert without needing to name them.

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 'instant or wall-clock' framing implicitly tells the agent when from_tz matters, and the example shows a canonical call. However, there is no explicit when-to-use/when-not guidance and no routing to alternatives for related needs (e.g. timestamp/epoch conversions handled elsewhere).

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