docs(time): fix example responses to match actual server output

[alvabillwu]

Summary

Fixes the example tool-call responses in src/time/README.md so they match what mcp-server-time actually returns. I verified the expected output against src/time/src/mcp_server_time/server.py (the TimeResult / TimeConversionResult models and the convert_time logic) and recomputed the conversions with Python's zoneinfo.

Problems fixed

1. get_current_time example response omitted the day_of_week field that TimeResult includes.

2. convert_time example response had several errors:

Field	Before	After	Why
source.datetime	2024-01-01T12:30:00-05:00	2024-01-01T16:30:00-05:00	the request used time: "16:30", not 12:30
source.day_of_week	(missing)	Monday	TimeResult includes it
target.datetime	2024-01-01T12:30:00+09:00	2024-01-02T06:30:00+09:00	16:30 EST → next-day 06:30 JST
target.day_of_week	(missing)	Tuesday	next calendar day
time_difference	+13.0h	+14.0h	on 2024-01-01 NY is EST (UTC−5), Tokyo is UTC+9 → +14h. (+13h only applies during US DST.)

3. Removed the trailing comma after time_difference (invalid JSON).

Verification

from datetime import datetime
from zoneinfo import ZoneInfo
src = datetime(2024,1,1,16,30,tzinfo=ZoneInfo("America/New_York"))
tgt = src.astimezone(ZoneInfo("Asia/Tokyo"))
# source: 2024-01-01T16:30:00-05:00  day=Monday  dst=False
# target: 2024-01-02T06:30:00+09:00  day=Tuesday dst=False
# time_difference: +14.0h

The time_difference format (+14.0h) matches the server's f"{hours_difference:+.1f}h" for integer offsets.

Doc-only change; no code or behavior affected.

🤖 Generated with Claude Code