Epoch Calculator

convert_timestamp

Read-onlyIdempotent

Convert a Unix timestamp (seconds or milliseconds; auto-detected unless unit is given) to a human-readable date in a time zone, with ISO 8601, RFC 2822, UTC offset, DST flag, weekday, and a relative phrase like "3 days ago".

Input Schema

TableJSON Schema

Name	Required	Description
`unit`	No	Interpretation of timestamp. Default auto.
`timezone`	No	IANA time zone, e.g. "America/New_York". Defaults to UTC.
`timestamp`	Yes	Unix timestamp. Values >= 1e11 are treated as milliseconds unless unit is set.

Output Schema

TableJSON Schema

Name	Required	Description
`iso`	Yes	ISO 8601 with the zone offset.
`human`	Yes	Readable sentence with weekday, date, time and zone.
`is_dst`	Yes	Whether daylight-saving time is in effect.
`offset`	Yes	UTC offset, e.g. "+09:00".
`rfc2822`	Yes	RFC 2822 date string.
`utc_iso`	Yes	ISO 8601 in UTC (Z).
`weekday`	Yes	Full weekday name in English.
`relative`	Yes	Relative phrase such as "3 days ago".
`timezone`	Yes	IANA zone name.
`abbreviation`	Yes	Zone abbreviation at that instant, e.g. "BST".
`epoch_millis`	Yes	Unix time in milliseconds.
`epoch_seconds`	Yes	Unix time in seconds.
`offset_minutes`	Yes	UTC offset in minutes.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "One instant described in one IANA time zone.",
+  "properties": {
+    "abbreviation": {
+      "description": "Zone abbreviation at that instant, e.g. \"BST\".",
+      "type": "string"
+    },
+    "epoch_millis": {
+      "description": "Unix time in milliseconds.",
+      "type": "integer"
+    },
+    "epoch_seconds": {
+      "description": "Unix time in seconds.",
+      "type": "integer"
+    },
+    "human": {
+      "description": "Readable sentence with weekday, date, time and zone.",
+      "type": "string"
+    },
+    "is_dst": {
+      "description": "Whether daylight-saving time is in effect.",
+      "type": "boolean"
+    },
+    "iso": {
+      "description": "ISO 8601 with the zone offset.",
+      "type": "string"
+    },
+    "offset": {
+      "description": "UTC offset, e.g. \"+09:00\".",
+      "type": "string"
+    },
+    "offset_minutes": {
+      "description": "UTC offset in minutes.",
+      "type": "integer"
+    },
+    "relative": {
+      "description": "Relative phrase such as \"3 days ago\".",
+      "type": "string"
+    },
+    "rfc2822": {
+      "description": "RFC 2822 date string.",
+      "type": "string"
+    },
+    "timezone": {
+      "description": "IANA zone name.",
+      "type": "string"
+    },
+    "utc_iso": {
+      "description": "ISO 8601 in UTC (Z).",
+      "type": "string"
+    },
+    "weekday": {
+      "description": "Full weekday name in English.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "epoch_seconds",
+    "epoch_millis",
+    "iso",
+    "utc_iso",
+    "timezone",
+    "offset",
+    "offset_minutes",
+    "abbreviation",
+    "is_dst",
+    "weekday",
+    "rfc2822",
+    "human",
+    "relative"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already signal read-only, idempotent, and non-destructive behavior, so the description does not need to repeat those. It adds useful behavioral detail about seconds/milliseconds auto-detection and exact output components, which goes beyond structured annotations.

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?

The core operation is front-loaded in one sentence, and the output format list is informative rather than filler. It is a bit dense, but every clause contributes useful selection or invocation information.

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?

Together with the schema, annotations, and output schema, the description covers what the tool does, accepted input units, time-zone handling, and what the result contains. No critical behavior is missing for a read-only formatting utility; edge-case error handling is left to schema or output docs.

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?

All three parameters are fully described in the input schema (coverage 100%), so the baseline is 3. The description mostly restates unit auto-detection and time-zone semantics that the schema already provides, adding no new parameter-level facts.

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 identifies a specific operation: converting a Unix timestamp into a human-readable date in a time zone, and enumerates the output fields (ISO 8601, RFC 2822, UTC offset, DST flag, weekday, relative phrase). This clearly distinguishes it from sibling tools such as convert_timezone or parse_datetime by centering on Unix timestamp input.

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 the appropriate use case—formatting a Unix timestamp into a calendar date—but does not explicitly name alternative tools or state when not to use it. With siblings like convert_timezone and epoch_math nearby, an agent gets inferred rather than explicit routing.

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

All Epoch Calculator tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct date/time operation: conversion, timezone shifting, cron scheduling, duration, countdown, arithmetic, parsing, and current time. Even the inverse operations (convert_timestamp vs parse_datetime) are clearly separated by input/output direction.

Naming Consistency3/5

Names are uniformly snake_case and readable, but they mix verb_noun patterns (convert_timestamp, parse_datetime) with noun-phrase or query-style names (date_duration, time_now, days_until, epoch_math, cron_next_runs). This is consistent in style but not in grammatical pattern.

Tool Count5/5

Eight tools is well-scoped for a date/time and epoch calculator. Each tool covers a distinct facet of the domain without redundancy or bloat.

Completeness5/5

The tool surface covers the full lifecycle of date/time operations: current time, parsing, formatting, timezone conversion, arithmetic, duration, countdowns, and cron scheduling. No significant gaps that would block common use cases.

Resources

Need Help?