Skip to content

mcp-server-time: Default Time Zone #2853

@daryltucker

Description

@daryltucker

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestserver-timeReference implementation for the Time MCP server - src/time

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions