time-mcp

get_time_in_timezone

Retrieve the current date and time for any IANA timezone. Provide the timezone (e.g., Asia/Tokyo, America/New_York) to get accurate local time.

Instructions

Return the current date and time in the given IANA timezone (e.g. Asia/Tokyo, America/New_York).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "timezone": "<timezone>"
    },
    "name": "get_time_in_timezone"
  }
}

Input Schema

Name	Required	Description	Default
`timezone`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral transparency. It clearly states the read-only behavior of returning current date and time, but does not disclose behavior for invalid timezone values, time source, or error conditions. This is adequate for a simple lookup tool but leaves some behavioral gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that immediately states the action and the required parameter format, with examples folded in naturally. There is no filler, repetition, or extraneous detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one required parameter and no output schema, the description is nearly sufficient. It covers the core purpose and parameter semantics, though it does not specify the response format or error behavior for invalid timezone strings. These are minor omissions given the tool's low complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only defines the parameter name 'timezone' with 0% description coverage. The tool description compensates by explaining that the value is an IANA timezone and provides two concrete examples, which adds essential semantic meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Return'), a clear resource ('current date and time in the given IANA timezone'), and includes concrete examples. This makes the tool's purpose immediately obvious and distinguishes it from siblings like get_local_time and list_timezones.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool: when a caller needs the current date/time for a specified IANA timezone. However, it does not explicitly state when not to use it or mention alternative tools, leaving the routing decision partially to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server