From 8f724ac4de6563a965802a410045fb57b6145002 Mon Sep 17 00:00:00 2001 From: Lumos-789 Date: Mon, 20 Jul 2026 01:27:13 +0800 Subject: [PATCH] fix(time): correct invalid IANA timezone example in convert_time description MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 'target_timezone' parameter description used 'America/San_Francisco' as an example, which is not a valid IANA timezone identifier — the tz database has no such key (San Francisco uses 'America/Los_Angeles'). Verification: >>> from zoneinfo import ZoneInfo >>> ZoneInfo('America/San_Francisco') ZoneInfoNotFoundError: No time zone found with key America/San_Francisco Impact: LLM clients consuming this description as a usage hint tend to copy example values verbatim. Passing 'America/San_Francisco' causes the server to reject the call with INVALID_PARAMS, surprising the user. Fix: replace with the valid 'America/Los_Angeles' identifier. This also brings target_timezone in line with the source_timezone description, which already correctly uses 'America/New_York' / 'Europe/London'. --- src/time/src/mcp_server_time/server.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/time/src/mcp_server_time/server.py b/src/time/src/mcp_server_time/server.py index 2cb0926134..4c970684b5 100644 --- a/src/time/src/mcp_server_time/server.py +++ b/src/time/src/mcp_server_time/server.py @@ -165,7 +165,7 @@ async def list_tools() -> list[Tool]: }, "target_timezone": { "type": "string", - "description": f"Target IANA timezone name (e.g., 'Asia/Tokyo', 'America/San_Francisco'). Use '{local_tz}' as local timezone if no target timezone provided by the user.", + "description": f"Target IANA timezone name (e.g., 'Asia/Tokyo', 'America/Los_Angeles'). Use '{local_tz}' as local timezone if no target timezone provided by the user.", }, }, "required": ["source_timezone", "time", "target_timezone"],