Date Math

Current date and time (free)

current_time

Read-only

Free: the current date, time, weekday and UTC offset in up to 10 time zones, plus UTC and Unix time. Use when today's date or the current time is needed. Does not use the daily free calls.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "current_time"
  }
}

Input Schema

Name	Required	Description	Default
`timezone`	No	IANA time zone, e.g. Asia/Manila
`timezones`	No	Up to 10 IANA time zones (default UTC)

Output Schema

Name	Required	Description	Default
`utc`	Yes
`times`	Yes
`unix_ms`	Yes
`unix_seconds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, consistent with a clock read. The description adds quota behavior (no consumption of daily free calls) and confirms always-returned fields, but says nothing about latency, rate limits, or invalid-timezone handling beyond the schema.

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

Conciseness4/5

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

Three short sentences, front-loaded with what is returned, then when to use it, then the quota property. Minor redundancy between the 'Free:' prefix and the final sentence about daily free calls.

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?

With an output schema, full param coverage and read-only annotations, the description needs only to state purpose, trigger and quota behavior, which it does. Only the relationship between the two timezone parameters and error behavior for invalid zones is left uncovered.

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%, including the IANA format, the 10-item cap and the UTC default, so the schema carries parameter meaning. The description only echoes the 10-timezone limit and does not clarify how the singular 'timezone' and plural 'timezones' parameters interact.

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 uses a specific resource (current date, time, weekday, UTC offset, UTC and Unix time) and states scope (up to 10 time zones). It implicitly distinguishes this from conversion/scheduling siblings by stressing 'current', though it names no sibling explicitly.

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

Usage Guidelines4/5

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

'Use when today's date or the current time is needed' gives a clear trigger condition, and the quota note ('Does not use the daily free calls') helps an agent prefer this over metered alternatives. There is no explicit when-not or named alternative (e.g. city_time, timezone_convert), so it falls short of a 5.

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

All Date Math tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.