Skip to main content
Glama

Epoch Calculator

by com.epochcalc

epoch_math

Read-only

Add to or subtract from a Unix timestamp in calendar-aware units (years, months, weeks, days, hours, minutes, seconds) in a time zone, e.g. "now + 30 days" or "1748736543 - 3 months". Returns the resulting timestamp in every format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNoUnits to add.
subtractNoUnits to subtract.
timezoneNoZone in which calendar units (months, days across DST) are applied. Defaults to UTC.
timestampNoBase Unix timestamp (seconds or milliseconds, auto-detected). Omit for now.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
baseYesOne instant described in one IANA time zone.
resultYesOne instant described in one IANA time zone.
delta_secondsYesresult minus base, in seconds.

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "base": {
+      "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"
+        },
+        "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"
+      ],
+      "type": "object"
+    },
+    "delta_seconds": {
+      "description": "result minus base, in seconds.",
+      "type": "integer"
+    },
+    "result": {
+      "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"
+        },
+        "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"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "base",
+    "result",
+    "delta_seconds"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: calendar-aware units, timezone sensitivity, and returning the result in every format. However, it does not disclose edge cases such as daylight-saving ambiguity or behavior when both add and subtract are supplied.

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 one well-constructed sentence that leads with the core operation, then specifies units, timezone, examples, and return behavior. Every clause adds information without redundancy.

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 core operation, units, timezone sensitivity, and return richness are all covered, and the output schema handles return-value structure. Minor gaps like behavior when both add and subtract are passed together are not addressed, but do not block correct use for standard calls.

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?

The input schema has 100% parameter description coverage, so the schema carries the weight for parameter meaning. The description adds value through call examples that show how timestamp, add/subtract, and timezone combine, but it does not elaborate on individual parameters beyond what the schema already states.

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 operation: adding or subtracting calendar-aware units from a Unix timestamp in a time zone. This distinguishes it clearly from conversion-focused siblings like convert_timestamp and convert_timezone. The concrete examples ('now + 30 days', '1748736543 - 3 months') make the purpose unmistakable.

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?

The description gives clear usage context through examples and states what the tool does with a timestamp. It does not explicitly name alternatives or exclusion conditions, but the operation is specific enough that an agent can infer when to use it rather than a converter or scheduler.

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

All Epoch Calculator toolsInspect
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