Timezone Convert

convert_time

Converts a local time in one IANA zone to up to 20 target zones. Returns local time, UTC offset, abbreviation and DST flag per target, and flags nonexistent or ambiguous local times at DST transitions.

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

Input Schema

Name	Required	Description	Default
`to`	Yes	Comma-separated target IANA zones, 1-20, e.g. Europe/London,Asia/Kolkata
`from`	Yes	Source IANA zone, e.g. America/New_York
`time`	Yes	ISO 8601 (2026-03-08T02:30:00, optional Z or offset) or 'YYYY-MM-DD HH:mm'. Without an offset it is read as local time in `from`
`ambiguous`	No	Which occurrence to use when the local time happens twice (fall-back). Default earlier (first, DST side)	earlier

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does well: it discloses the return shape (local time, UTC offset, abbreviation, DST flag) and, importantly, that nonexistent or ambiguous local times at DST transitions are flagged. It stops short of stating error behavior for invalid zones or how the flags are surfaced in the response.

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?

Two compact sentences with no filler; the core conversion behavior comes first and the output/DST caveats follow. Nothing here restates the name gratuitously.

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?

There is no output schema, and the description compensates by enumerating the returned fields and the DST-flagging behavior, which is what an agent needs to trust the result. Minor gap: nothing about invalid input handling or the 20-zone limit's failure mode, though the schema already caps it.

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 four parameters, including the ambiguous enum and its default, are fully documented structurally. The description adds only the fact that DST anomalies are flagged, which barely extends what the schema's ambiguous field already explains; baseline 3 applies.

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?

States a specific verb and resource ('Converts a local time in one IANA zone to up to 20 target zones') and names the output fields. Clear enough to act on, but it never differentiates itself from the siblings zone_info and overlap_hours, so an agent must infer which one to pick.

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?

Usage is only implied by the described behavior: convert a time, plural targets allowed. There is no explicit 'use this when...', no exclusion against zone_info (for zone metadata) or overlap_hours (for finding common working hours), and no mention of prerequisites such as valid IANA identifiers.

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

All Timezone Convert tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?