tilwhen date engine is an MCP server published by com.tilwhen, hosted at mcp.tilwhen.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 9 tools, including parse_date_query, add_days, subtract_days, days_between, business_days.
Deterministic date arithmetic with auditable receipts: business days, due dates, holidays.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Parses queries like "90 business days from today in uganda" into a normalized operation, answers it, and returns the auditable receipt. Ambiguous dates (03/04/2027) return needsClarification instead of a guess.
| Parameter | Type | Description |
|---|---|---|
| q * | string | The date question in plain language. Pass the user's wording rather than a date you computed. |
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| locale | string | Resolves ambiguous slash dates; omit to receive clarification choices |
None yet. Changes appear after a server's second daily check.
Inferred from the host name and headers: what a server runs on, not who runs it.
{
"name": "parse_date_query",
"title": "Parse a natural-language date question",
"description": "Parses queries like \"90 business days from today in uganda\" into a normalized operation, answers it, and returns the auditable receipt. Ambiguous dates (03/04/2027) return needsClarification instead of a guess.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"q"
],
"properties": {
"q": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The date question in plain language. Pass the user's wording rather than a date you computed."
},
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"locale": {
"enum": [
"mdy",
"dmy"
],
"type": "string",
"description": "Resolves ambiguous slash dates; omit to receive clarification choices"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"parsed",
"confidence",
"warnings"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer, absent when parsed is null",
"additionalProperties": true
},
"parsed": {
"anyOf": [
{
"type": "object",
"properties": {},
"additionalProperties": true
},
{
"type": "null"
}
],
"description": "Normalized operation, or null when the query could not be understood confidently"
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt, absent when parsed is null",
"additionalProperties": true
},
"warnings": {
"type": "array",
"items": {
"type": "string"
},
"description": "Machine-readable notes, e.g. unsupported_unit or time_ignored"
},
"confidence": {
"type": "number",
"description": "1.0 is a clean grammar hit; below 0.5 the query is refused rather than guessed"
},
"canonicalUrl": {
"type": [
"string",
"null"
],
"description": "tilwhen page that answers this query, to cite; null when no page covers it"
},
"needsClarification": {
"type": "object",
"properties": {},
"description": "Present when the query is genuinely ambiguous (e.g. 03/04/2027); offers explicit choices instead of a guess",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}The date N whole calendar days after a date (exclusive counting: the start date is day 0). Omit date for today in tz. For working days use business_days; for the gap between two dates use days_between.
| Parameter | Type | Description |
|---|---|---|
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| date | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days * | integer | Whole calendar days to add. Negative counts backwards. |
{
"name": "add_days",
"title": "Add calendar days to a date",
"description": "The date N whole calendar days after a date (exclusive counting: the start date is day 0). Omit date for today in tz. For working days use business_days; for the gap between two dates use days_between.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"days"
],
"properties": {
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"date": {
"type": "string",
"default": "today",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"days": {
"type": "integer",
"maximum": 100000,
"minimum": -100000,
"description": "Whole calendar days to add. Negative counts backwards."
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answer",
"receipt"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer (kind-discriminated)",
"additionalProperties": true
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}The date N whole calendar days before a date (exclusive counting: the start date is day 0). Omit date for today in tz. For working days use business_days; for the gap between two dates use days_between.
| Parameter | Type | Description |
|---|---|---|
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| date | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days * | integer | Whole calendar days to subtract. Negative counts forwards. |
{
"name": "subtract_days",
"title": "Subtract calendar days from a date",
"description": "The date N whole calendar days before a date (exclusive counting: the start date is day 0). Omit date for today in tz. For working days use business_days; for the gap between two dates use days_between.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"days"
],
"properties": {
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"date": {
"type": "string",
"default": "today",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"days": {
"type": "integer",
"maximum": 100000,
"minimum": -100000,
"description": "Whole calendar days to subtract. Negative counts forwards."
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answer",
"receipt"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer (kind-discriminated)",
"additionalProperties": true
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Signed whole calendar days from the from date to the to date, midnight to midnight in tz: positive when to is later, negative when it is earlier. Endpoints are exclusive, so this is the gap and consecutive dates are 1 apart. Either date may be "today", resolved in tz. For working days between two dates use business_days; to move a date by N days use add_days or subtract_days.
| Parameter | Type | Description |
|---|---|---|
| to * | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| from * | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
{
"name": "days_between",
"title": "Days between two dates",
"description": "Signed whole calendar days from the from date to the to date, midnight to midnight in tz: positive when to is later, negative when it is earlier. Endpoints are exclusive, so this is the gap and consecutive dates are 1 apart. Either date may be \"today\", resolved in tz. For working days between two dates use business_days; to move a date by N days use add_days or subtract_days.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"from",
"to"
],
"properties": {
"to": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"from": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answer",
"receipt"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer (kind-discriminated)",
"additionalProperties": true
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Span mode (from+to): business days between two dates, exclusive of the start day, inclusive of the end day. Add mode (days, optional date): the date N business days away. Passing from or to selects span mode and needs both; days and date are then ignored, so add mode takes its start date in date, not from. Optional holiday jurisdiction or custom calendar, and a selectable working week. For calendar days use add_days, subtract_days or days_between.
| Parameter | Type | Description |
|---|---|---|
| to | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| date | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | Add mode: business days to move. Negative counts backwards. |
| from | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| workweek | string | Working week. Default mon-fri (Sat+Sun weekend). |
| jurisdiction | string | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar. |
| customHolidays | array | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
{
"name": "business_days",
"title": "Business-day calculations",
"description": "Span mode (from+to): business days between two dates, exclusive of the start day, inclusive of the end day. Add mode (days, optional date): the date N business days away. Passing from or to selects span mode and needs both; days and date are then ignored, so add mode takes its start date in date, not from. Optional holiday jurisdiction or custom calendar, and a selectable working week. For calendar days use add_days, subtract_days or days_between.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"to": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"days": {
"type": "integer",
"maximum": 100000,
"minimum": -100000,
"description": "Add mode: business days to move. Negative counts backwards."
},
"from": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"workweek": {
"enum": [
"mon-fri",
"sun-thu",
"mon-sat"
],
"type": "string",
"description": "Working week. Default mon-fri (Sat+Sun weekend)."
},
"jurisdiction": {
"type": "string",
"maxLength": 8,
"description": "Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar."
},
"customHolidays": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 1000,
"description": "Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction)"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answer",
"receipt"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer (kind-discriminated)",
"additionalProperties": true
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Due date for Net-N payment terms (calendar days, invoice date = day 0). Optional roll-forward past weekends and, with a jurisdiction or custom calendar, public holidays.
| Parameter | Type | Description |
|---|---|---|
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| net * | integer | Net-N payment terms in calendar days (Net 30 = 30). |
| roll | boolean | Roll a weekend or holiday due date forward to the next business day. Default false. |
| workweek | string | Working week. Default mon-fri (Sat+Sun weekend). |
| invoiceDate | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| jurisdiction | string | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar. |
| customHolidays | array | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
{
"name": "invoice_due",
"title": "Invoice due date from net terms",
"description": "Due date for Net-N payment terms (calendar days, invoice date = day 0). Optional roll-forward past weekends and, with a jurisdiction or custom calendar, public holidays.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"net"
],
"properties": {
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"net": {
"type": "integer",
"maximum": 3650,
"minimum": 0,
"description": "Net-N payment terms in calendar days (Net 30 = 30)."
},
"roll": {
"type": "boolean",
"description": "Roll a weekend or holiday due date forward to the next business day. Default false."
},
"workweek": {
"enum": [
"mon-fri",
"sun-thu",
"mon-sat"
],
"type": "string",
"description": "Working week. Default mon-fri (Sat+Sun weekend)."
},
"invoiceDate": {
"type": "string",
"default": "today",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"jurisdiction": {
"type": "string",
"maxLength": 8,
"description": "Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar."
},
"customHolidays": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 1000,
"description": "Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction)"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answer",
"receipt"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer (kind-discriminated)",
"additionalProperties": true
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}The next occurrence strictly after the base date (default today) of either a tracked event slug (e.g. "christmas") or a weekday (0 = Sunday .. 6 = Saturday). Provide exactly one of event/weekday.
| Parameter | Type | Description |
|---|---|---|
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| from | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| event | string | Event slug (e.g. christmas). Exactly one of event/weekday. |
| weekday | integer | 0 = Sunday .. 6 = Saturday. Exactly one of event/weekday. |
{
"name": "next_occurrence",
"title": "Next occurrence of an event or weekday",
"description": "The next occurrence strictly after the base date (default today) of either a tracked event slug (e.g. \"christmas\") or a weekday (0 = Sunday .. 6 = Saturday). Provide exactly one of event/weekday.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"from": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"event": {
"type": "string",
"maxLength": 40,
"description": "Event slug (e.g. christmas). Exactly one of event/weekday."
},
"weekday": {
"type": "integer",
"maximum": 6,
"minimum": 0,
"description": "0 = Sunday .. 6 = Saturday. Exactly one of event/weekday."
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answer",
"receipt"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer (kind-discriminated)",
"additionalProperties": true
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Observed public holidays with the nominal (legal) date and status: rule (statutory) or declared (officially declared for that year). Declared-only holidays are omitted for undeclared years, with a holiday_data_incomplete warning.
| Parameter | Type | Description |
|---|---|---|
| year * | integer | Calendar year to list, e.g. 2027 |
| jurisdiction * | string | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). |
{
"name": "holidays",
"title": "Public holidays for a jurisdiction and year",
"description": "Observed public holidays with the nominal (legal) date and status: rule (statutory) or declared (officially declared for that year). Declared-only holidays are omitted for undeclared years, with a holiday_data_incomplete warning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"jurisdiction",
"year"
],
"properties": {
"year": {
"type": "integer",
"maximum": 3000,
"minimum": 1600,
"description": "Calendar year to list, e.g. 2027"
},
"jurisdiction": {
"type": "string",
"maxLength": 8,
"description": "Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB)."
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"answer",
"receipt"
],
"properties": {
"answer": {
"type": "object",
"properties": {},
"description": "The calculated answer (kind-discriminated)",
"additionalProperties": true
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Runs any operation and returns the receipt plus human-readable derivation steps. Set op, then pass the fields that operation's own tool takes. Use it when the user asks how an answer was reached.
| Parameter | Type | Description |
|---|---|---|
| op * | string | Operation to explain. holiday_lookup is the holidays tool; the others share their tool's name. |
| to | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| net | integer | Net-N payment terms in calendar days (Net 30 = 30). |
| date | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | Day count for add_days, subtract_days and business_days add mode. |
| from | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| roll | boolean | Roll a weekend or holiday due date forward to the next business day. Default false. |
| year | integer | Calendar year for holiday_lookup, e.g. 2027 |
| event | string | Event slug (e.g. christmas). Exactly one of event/weekday. |
| weekday | integer | 0 = Sunday .. 6 = Saturday. Exactly one of event/weekday. |
| workweek | string | Working week. Default mon-fri (Sat+Sun weekend). |
| invoiceDate | string | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| jurisdiction | string | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar. |
| customHolidays | array | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
{
"name": "explain",
"title": "Explain a calculation step by step",
"description": "Runs any operation and returns the receipt plus human-readable derivation steps. Set op, then pass the fields that operation's own tool takes. Use it when the user asks how an answer was reached.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"op"
],
"properties": {
"op": {
"enum": [
"add_days",
"subtract_days",
"days_between",
"business_days",
"invoice_due",
"next_occurrence",
"holiday_lookup"
],
"type": "string",
"description": "Operation to explain. holiday_lookup is the holidays tool; the others share their tool's name."
},
"to": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"tz": {
"type": "string",
"default": "UTC",
"maxLength": 64,
"description": "IANA timezone that defines \"today\" (e.g. Africa/Kampala). Default UTC."
},
"net": {
"type": "integer",
"maximum": 3650,
"minimum": 0,
"description": "Net-N payment terms in calendar days (Net 30 = 30)."
},
"date": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"days": {
"type": "integer",
"maximum": 100000,
"minimum": -100000,
"description": "Day count for add_days, subtract_days and business_days add mode."
},
"from": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"roll": {
"type": "boolean",
"description": "Roll a weekend or holiday due date forward to the next business day. Default false."
},
"year": {
"type": "integer",
"maximum": 3000,
"minimum": 1600,
"description": "Calendar year for holiday_lookup, e.g. 2027"
},
"event": {
"type": "string",
"maxLength": 40,
"description": "Event slug (e.g. christmas). Exactly one of event/weekday."
},
"weekday": {
"type": "integer",
"maximum": 6,
"minimum": 0,
"description": "0 = Sunday .. 6 = Saturday. Exactly one of event/weekday."
},
"workweek": {
"enum": [
"mon-fri",
"sun-thu",
"mon-sat"
],
"type": "string",
"description": "Working week. Default mon-fri (Sat+Sun weekend)."
},
"invoiceDate": {
"type": "string",
"pattern": "^(\\d{4}-\\d{2}-\\d{2}|today)$",
"description": "ISO date YYYY-MM-DD, or \"today\" (resolved in tz)"
},
"jurisdiction": {
"type": "string",
"maxLength": 8,
"description": "Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar."
},
"customHolidays": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 1000,
"description": "Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction)"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"receipt",
"steps"
],
"properties": {
"steps": {
"type": "array",
"items": {
"type": "string"
},
"description": "Human-readable derivation, identical to the REST /api/v1/explain output"
},
"receipt": {
"type": "object",
"properties": {},
"description": "Auditable receipt for the operation",
"additionalProperties": true
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}tilwhen answers date questions deterministically and shows its working. Every tool returns a receipt alongside the answer: the normalized operation, the pinned input dates, the IANA timezone, the counting convention, the working week, the holiday calendar with each excluded holiday itemised, the primary sources with retrieval dates, engine and dataset versions, and a stable result ID that is a deterministic hash of inputs and versions. Cite the answer with its validFor date, timezone and result ID; the same question under the same versions reproduces it. Conventions that change answers, so state them when you report one: - Whole calendar days, midnight to midnight, in the requested IANA timezone. `tz` is an explicit input and defaults to UTC; it is the only thing that decides which calendar day "today" is. Pass the user's timezone when you know it. - Counting is exclusive: today is day 0 and is not counted. - Business days exclude the start day and include the end day. - There is NO default holiday calendar. Omit the jurisdiction and no holidays are excluded, and the receipt says so. Never infer one from a timezone or a locale; ask the user which calendar they mean. - Holidays whose date is declared per year rather than fixed by rule are included only for officially declared years. A span crossing an undeclared year returns a holiday_data_incomplete warning; report the warning rather than the bare number. Prefer these tools over computing dates yourself: the failure mode of doing this arithmetic in your head is a confident answer that is wrong by one day.
Names, descriptions and schemas were written by the server and are shown as data.