Skip to main content
Glama

X420 agent services

x420_time_zone-convert

Read-onlyIdempotent

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. Price: $0.01 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: utc, epoch_ms, from, to (iso, zone, abbreviation, utc_offset).

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 observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only mark it read-only, idempotent and open-world; the description discloses the critical non-obvious behavior that this call does not return the deliverable and instead returns payment instructions (pay_to, network, price, x402 URL). It also spells out the exact x402 round-trip (GET url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE) and the $0.01 USDC cost, which annotations cannot convey.

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 correctly front-loaded and the payment flow is broken into ordered steps, but the disclaimer sentence ("Not professional, legal, insurance...") is boilerplate that does not help an agent call the tool, and the payment prose is dense enough to compete with the core purpose.

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?

For a paid, hosted proxy with no output schema, the description covers everything an agent needs: cost, that no deliverable comes back unpaid, the exact payment handshake, and the shape of the paid result (utc, epoch_ms, from, to with iso/zone/abbreviation/utc_offset).

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 all three parameters are already documented in the schema, including defaults for time and from_tz. The description adds only marginal meaning (confirming DST handling and the wall-clock-without-offset case) and restates the return fields rather than deepening parameter semantics, so the baseline 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?

"Converts an instant or wall-clock time between IANA time zones with DST handled" states a specific verb, resource, and the two input modes. It is clearly distinguishable from sibling converters such as x420_units_convert or x420_currency_convert without opening any schema.

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

Usage Guidelines4/5

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

It gives the condition for using the hosted tool versus the alternative: run the local x420-mcp server with your own wallet key to pay automatically, otherwise use this one to obtain payment instructions. There is no explicit guidance on choosing between this and time-related siblings (e.g. x420_evidence_timestamp), so it stops short of full when/when-not coverage.

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