my-first-server

Get current time

get_current_time

Get the current date and time, with optional IANA timezone support to display the time in any global region.

Instructions

Returns the current date and time. Optionally pass an IANA timezone (e.g. 'Asia/Kolkata', 'America/New_York') to get the time there.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`timezone`	No	IANA timezone name, e.g. 'Asia/Kolkata'. Defaults to the server's local time.

Output Schema

TableJSON Schema

Name	Required	Description
`iso`	Yes	ISO 8601 timestamp
`timezone`	Yes	The IANA timezone the result is expressed in
`unixSeconds`	Yes	Seconds since the Unix epoch

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 14, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It conveys the core read-only behavior and optional timezone behavior, but does not mention edge cases like invalid timezone handling or output format. The output schema presumably covers return structure, but some informational context is still missing.

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, front-loaded sentence: the main purpose comes first, and the optional parameter detail follows. Every word earns its place, with no filler or repetition.

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 optional parameter and an output schema, the description provides the essential information to invoke it correctly. It covers the default behavior and the optional timezone usage. Error behavior for invalid timezone is not described, but that is a minor gap given the tool's simplicity.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents the timezone parameter. The description adds helpful IANA examples and clarifies the optionality and purpose of the parameter, but it does not provide substantial meaning beyond the schema.

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

Purpose4/5

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

The description clearly states the operation ('Returns the current date and time') and the resource, making the tool's purpose unmistakable. It does not explicitly differentiate from sibling stream_load, but the purpose is precise enough that no confusion is likely.

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: whenever the current date/time is needed. It also explains the optional timezone parameter. However, it does not explicitly state exclusions or compare against alternatives beyond that implied context.

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

Deploy Server