Timeapi Io

Current Zone Info

current_zone_info

Read-onlyIdempotent

Return timezone metadata for an IANA zone name: UTC offset, DST offset, current offset, DST start/end, and whether DST is currently active.

Input Schema

Name	Required	Description	Default
`timeZone`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "timeZone": "America/Los_Angeles"
+  },
+  {
+    "timeZone": "Europe/Paris"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Timezone information",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld hints. The description adds concrete details on the returned metadata (offsets, DST start/end, active status), providing transparency beyond annotations.

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?

Single sentence, no waste. Directly lists the information returned.

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?

The description covers the key outputs. Given the output schema exists, it doesn't need to detail return structure. However, it could mention error handling or input validation.

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

Parameters2/5

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

With 0% schema description coverage, the description carries full burden but only mentions 'IANA zone name'. It does not specify the expected format (e.g., 'America/New_York') or provide examples beyond the schema examples.

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 clearly states the tool returns timezone metadata for an IANA zone name, listing specific fields such as UTC offset, DST offset, etc. This differentiates it from sibling tools like convert_time_zone or list_zones.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like convert_time_zone. No explicit when-to-use or when-not-to-use context is provided.

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

All Timeapi Io 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.