mcp-server-time: Default Time Zone

I feel like forcing specification of a timezone is wasteful, and --local-timezone should be the default when unspecified via tool request.

When mcp-server-time is provided --local-timezone, the LLM should not have to specify the time.

1. Wasteful, error-prone with previous behavior
2. The LLM could learn the TZ simply by looking up the time with this behavior

I am wasting too much context enforcing LLMs to specify the timezone. It doesn't make sense to them, and it doesn't make sense to me either.

{
"error": "HTTP error 422: {\"detail\":[{\"type\":\"missing\",\"loc\":[\"body\",\"timezone\"],\"msg\":\"Field required\",\"input\":{}}]}"
}

"error": "500: {'message': 'Error processing mcp-server-time query: Missing required argument: timezone'}"

{
  "detail": [
    {
      "type": "missing",
      "loc": [
        "body",
        "timezone"
      ],
      "msg": "Field required",
      "input": {}
    }
  ]
}

Is this behavior already available and I am missing something?

Start by locating the mcp-server-time implementation and the handling for the timezone argument and --local-timezone option. Check existing tests for time requests, if present. Done means a request that omits timezone uses the local timezone when --local-timezone is supplied, without producing the reported validation errors.