OnlineCyberTools MCP (280+ filterable tools)

time_date_calculator

Read-onlyIdempotent

Add or subtract years, months, weeks, or days from a base date, or shift by business days that skip weekends. Returns the resulting date and total days shifted.

Instructions

Date Calculator (Add/Subtract Duration and Business Days). Add or subtract a years/months/weeks/days duration from an explicit base date, or add a signed number of business days that skips weekends, using proleptic-Gregorian UTC arithmetic. Years and months apply first with the day-of-month clamped to the last valid day (Jan 31 + 1 month is Feb 28/29, never Mar 3), then the week/day shift. Use this when you have a known start date and want the resulting date; use time_date_difference to measure the span between two dates, or time_time_duration for HH:MM:SS clock arithmetic. The caller supplies every date, so results are deterministic (no current-time dependency). Runs locally: read-only, non-destructive, contacts no external service, and is rate-limited (60 requests/minute for anonymous callers). Returns the base and result dates (year/month/day, ISO date, weekday) plus the total days shifted and, for business-day mode, the weekends skipped.

Input Schema

TableJSON Schema

Name	Required	Description
`operation`	Yes	Which calculation to run: "add" or "subtract" a calendar duration, or "addBusinessDays" to shift by weekday-only days.
`year`	Yes	Base date year (proleptic Gregorian).
`month`	Yes	Base date month, 1 (January) to 12 (December).
`day`	Yes	Base date day of month; must be a real calendar day for the given year/month.
`years`	No	Years to add (add/subtract only; ignored for addBusinessDays).
`months`	No	Months to add (add/subtract only; ignored for addBusinessDays).
`weeks`	No	Weeks to add (add/subtract only; ignored for addBusinessDays).
`days`	No	Days to shift. For add/subtract, a calendar-day component in -1000..1000 (default 0); for addBusinessDays, a signed weekday-only count in -100000..100000 (negative walks backward). For add/subtract, at least one of years/months/weeks/days must be non-zero.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`operation`	No	Echo of the requested operation (add, subtract, or addBusinessDays).
`data`	No	Result payload. Always includes base and result; add/subtract add totalDaysAdded and breakdown, addBusinessDays adds daysAdded, weekendsSkipped, and totalCalendarDaysShifted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed29 schema fields changedv0.5.1Jun 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / day / description

Added value: +"Base date day of month; must be a real calendar day for the given year/month."

addedInput schema / properties / day / maximum
```
Added value: +31
```
addedInput schema / properties / day / minimum
```
Added value: +1
```

addedInput schema / properties / days / description

Added value: +"Days to shift. For add/subtract, a calendar-day component in -1000..1000 (default 0); for addBusinessDays, a signed weekday-only count in -100000..100000 (negative walks backward). For add/subtract, at least one of years/months/weeks/days must be non-zero."

addedInput schema / properties / days / maximum
```
Added value: +100000
```
addedInput schema / properties / days / minimum
```
Added value: +-100000
```

addedInput schema / properties / month / description

Added value: +"Base date month, 1 (January) to 12 (December)."

addedInput schema / properties / month / maximum
```
Added value: +12
```
addedInput schema / properties / month / minimum
```
Added value: +1
```
addedInput schema / properties / months / default
```
Added value: +0
```

addedInput schema / properties / months / description

Added value: +"Months to add (add/subtract only; ignored for addBusinessDays)."

addedInput schema / properties / months / maximum
```
Added value: +1000
```
addedInput schema / properties / months / minimum
```
Added value: +-1000
```

addedInput schema / properties / operation / description

Added value: +"Which calculation to run: \"add\" or \"subtract\" a calendar duration, or \"addBusinessDays\" to shift by weekday-only days."

addedInput schema / properties / operation / enum

Added value: +[
+  "add",
+  "subtract",
+  "addBusinessDays"
+]

addedInput schema / properties / weeks / default
```
Added value: +0
```

addedInput schema / properties / weeks / description

Added value: +"Weeks to add (add/subtract only; ignored for addBusinessDays)."

addedInput schema / properties / weeks / maximum
```
Added value: +1000
```
addedInput schema / properties / weeks / minimum
```
Added value: +-1000
```

addedInput schema / properties / year / description

Added value: +"Base date year (proleptic Gregorian)."

addedInput schema / properties / year / maximum
```
Added value: +9999
```
addedInput schema / properties / year / minimum
```
Added value: +-9999
```
addedInput schema / properties / years / default
```
Added value: +0
```

addedInput schema / properties / years / description

Added value: +"Years to add (add/subtract only; ignored for addBusinessDays)."

addedInput schema / properties / years / maximum
```
Added value: +1000
```
addedInput schema / properties / years / minimum
```
Added value: +-1000
```

changedInput schema / required

Previous value: -[
-  "operation",
-  "year",
-  "month",
-  "day",
-  "years",
-  "months",
-  "weeks",
-  "days"
-]New value: +[
+  "operation",
+  "year",
+  "month",
+  "day"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Result payload. Always includes base and result; add/subtract add totalDaysAdded and breakdown, addBusinessDays adds daysAdded, weekendsSkipped, and totalCalendarDaysShifted.",
+      "properties": {
+        "base": {
+          "description": "The supplied base date.",
+          "properties": {
+            "day": {
+              "description": "Base date day of month.",
+              "type": "integer"
+            },
+            "dayOfWeek": {
+              "description": "Base date weekday name, Sunday-Saturday.",
+              "type": "string"
+            },
+            "isoDate": {
+              "description": "Base date as YYYY-MM-DD (UTC).",
+              "type": "string"
+            },
+            "month": {
+              "description": "Base date month, 1-12.",
+              "type": "integer"
+            },
+            "year": {
+              "description": "Base date year.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "breakdown": {
+          "description": "add/subtract only: the input duration as given.",
+          "properties": {
+            "days": {
+              "description": "Days component as supplied.",
+              "type": "integer"
+            },
+            "months": {
+              "description": "Months component as supplied.",
+              "type": "integer"
+            },
+            "weeks": {
+              "description": "Weeks component as supplied.",
+              "type": "integer"
+            },
+            "years": {
+              "description": "Years component as supplied.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "daysAdded": {
+          "description": "addBusinessDays only: signed business-day count as supplied.",
+          "type": "integer"
+        },
+        "result": {
+          "description": "The resulting date after the shift.",
+          "properties": {
+            "day": {
+              "description": "Result day of month.",
+              "type": "integer"
+            },
+            "dayOfWeek": {
+              "description": "Result weekday name, Sunday-Saturday.",
+              "type": "string"
+            },
+            "isoDate": {
+              "description": "Result date as YYYY-MM-DD (UTC).",
+              "type": "string"
+            },
+            "month": {
+              "description": "Result month, 1-12.",
+              "type": "integer"
+            },
+            "year": {
+              "description": "Result year.",
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "totalCalendarDaysShifted": {
+          "description": "addBusinessDays only: total calendar days walked (business days plus weekends skipped).",
+          "type": "integer"
+        },
+        "totalDaysAdded": {
+          "description": "add/subtract only: signed (result - base) in whole days.",
+          "type": "integer"
+        },
+        "weekendsSkipped": {
+          "description": "addBusinessDays only: number of weekend days walked over.",
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    },
+    "operation": {
+      "description": "Echo of the requested operation (add, subtract, or addBusinessDays).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedv0.1.0May 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint), the description adds behavioral details: runs locally, read-only, rate-limited, and explains business day arithmetic and month clamping. No contradiction; all are consistent with 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 description is a single paragraph but is information-dense and well-front-loaded. Every sentence adds value, though breaking into bullet points could improve scannability. Still, it's concise for the amount of information.

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?

Given the tool's complexity (8 parameters, business day logic, edge cases), the description covers input behavior (clamping), output format (returns base/result dates, total days, weekends skipped), constraints (rate limit, local execution), and non-destructiveness. Complete and sufficient.

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

Parameters5/5

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

While the schema covers 100% of parameters, the description adds crucial semantics: explains the order of operations for years/months clamping, and details the behavior of 'days' for business days vs calendar days. This goes beyond the schema's basic 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 clearly states the tool's purpose: 'Date Calculator (Add/Subtract Duration and Business Days)'. It explicitly distinguishes from sibling tools like time_date_difference and time_time_duration, making it easy for an agent to select the correct tool.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: 'Use this when you have a known start date and want the resulting date' and directs to alternatives for other scenarios. It also notes deterministic behavior and no current-time dependency, aiding appropriate invocation.

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

Deploy Server