Skip to main content
Glama

Time zone converter

time_convert

Use when an agent is about to commit to a time in someone else's zone and cannot be an hour wrong: converts between any two IANA zones with daylight saving applied from the runtime's own tz database. Returns both sides with their UTC offset, abbreviation and DST flag, plus the UTC instant and the difference in hours. Warns when the time asked for does not exist or happens twice because the clocks change that day: the two cases that quietly make a hand-made conversion wrong. $0.0018 per call, paid over x402 (USDC).

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

Input Schema

NameRequiredDescriptionDefault
toYesTarget IANA time zone, e.g. "Asia/Tokyo". Required.
fromYesSource IANA time zone, e.g. "Europe/Madrid". Required.
timeNoWall clock as YYYY-MM-DD HH:MM in the "from" zone, or an ISO string with Z or an offset, or a unix timestamp, or "now". Defaults to now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses DST handling from the runtime tz database, the returned fields, warnings for nonexistent or duplicated local times, and the per-call price paid over x402 in USDC.

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 description is front-loaded with the usage condition, then adds return behavior, warning behavior, and cost in compact sentences. Every sentence contributes distinct decision-relevant information with no filler.

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 three-parameter conversion tool with no output schema and no annotations, the description is complete enough: it explains the conversion, DST application, return fields, ambiguous/nonexistent time warnings, and payment requirements. No obvious prerequisite for correct invocation is missing.

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 coverage is 100%, and the schema already documents from and to as IANA zones and time as accepting multiple formats plus 'now'. The description reinforces the IANA-zone and edge-case meaning but adds no syntax or formatting guidance beyond the schema, so the baseline 3 is appropriate.

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 between any two IANA time zones with daylight saving applied. It also distinguishes itself from a naive time lookup by calling out nonexistent and ambiguous local times, so an agent can tell this is a conversion tool rather than a current-time or zone-list tool.

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?

Gives clear usage context: use when committing to a time in someone else's zone and cannot be an hour wrong. It does not explicitly name alternatives such as time_now or time_zones, nor does it state when not to use it, so it stops short of a 5.

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