Skip to main content
Glama

Epoch Calculator

by com.epochcalc

days_until

Read-only

Countdown to a holiday or to a date: days, hours and minutes remaining, and the next occurrence date. Pass an event slug (e.g. "christmas", "thanksgiving", "easter", "super-bowl") or a date (YYYY-MM-DD). Call with no arguments to list the known events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoA target date (YYYY-MM-DD) or date-time (ISO 8601) instead of an event.
eventNoEvent slug from the known list, e.g. "christmas".
timezoneNoZone whose midnight starts the target day. Defaults to UTC.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
nameNo
hoursNo
humanNoe.g. "in 12 days, 5 hours".
eventsNoKnown events (only when called with no arguments).
targetNoOne instant described in one IANA time zone.
is_pastNo
minutesNo
total_secondsNo

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: +{
+  "description": "With an event or date: the countdown fields. With no arguments: only the events list.",
+  "properties": {
+    "days": {
+      "type": "integer"
+    },
+    "events": {
+      "description": "Known events (only when called with no arguments).",
+      "items": {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "slug",
+          "name"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "hours": {
+      "type": "integer"
+    },
+    "human": {
+      "description": "e.g. \"in 12 days, 5 hours\".",
+      "type": "string"
+    },
+    "is_past": {
+      "type": "boolean"
+    },
+    "minutes": {
+      "type": "integer"
+    },
+    "name": {
+      "type": "string"
+    },
+    "target": {
+      "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"
+    },
+    "total_seconds": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this read-only and non-destructive. The description adds practical behavioral details beyond those annotations: it reports days, hours, minutes, and next occurrence, and that calling with no arguments lists known events. This is useful context an agent cannot infer from the annotations alone.

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 compact, front-loads the outcome, and uses two sentences to cover purpose, accepted inputs, examples, and the discovery mechanism. Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only countdown tool with no required parameters and a full input schema plus an output schema, the description covers the important usage variations: event slug, custom date, timezone, and listing known events. Nothing critical is missing for an agent to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all three parameters. The description adds complementary meaning by explaining the event-vs-date choice, providing example slugs, specifying the YYYY-MM-DD format, and noting the no-argument behavior, which goes beyond the bare schema descriptions.

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 uses a specific verb and resource: it 'Countdown to a holiday or to a date' and specifies exactly what is returned. It clearly distinguishes this from the sibling time/date tools by focusing on countdown and next occurrence, not conversion or parsing.

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 modes: pass an event slug, pass a date, or call with no arguments to list known events. It does not explicitly contrast this with sibling tools like date_duration or time_now, but the intended usage is unambiguous.

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