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.
- Wasteful, error-prone with previous behavior
- 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?
I feel like forcing specification of a timezone is wasteful, and
--local-timezoneshould be the default when unspecified via tool request.When
mcp-server-timeis provided--local-timezone, the LLM should not have to specify the time.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\":{}}]}" }Is this behavior already available and I am missing something?