wikifeed

On This Day

on_this_day

Read-onlyIdempotent

Get historical events, births, deaths, and holidays that occurred on a given month and day across all years.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`day`	Yes	Two-digit day number (e.g., "01", "15", "31")
`month`	Yes	Two-digit month number (e.g., "01" for January, "12" for December)

Output Schema

TableJSON Schema

Name	Required	Description
`day`	Yes	Two-digit day number provided
`month`	Yes	Two-digit month number provided
`births`	Yes	Notable births on this day
`deaths`	Yes	Notable deaths on this day
`events`	Yes	Historical events on this day
`holidays`	Yes	Holidays and observances on this day

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "births": {
+      "description": "Notable births on this day",
+      "items": {
+        "properties": {
+          "pages": {
+            "description": "Related Wikipedia article titles",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "text": {
+            "description": "Description of the person",
+            "type": "string"
+          },
+          "year": {
+            "description": "Year of birth",
+            "type": "number"
+          }
+        },
+        "required": [
+          "year",
+          "text",
+          "pages"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "day": {
+      "description": "Two-digit day number provided",
+      "type": "string"
+    },
+    "deaths": {
+      "description": "Notable deaths on this day",
+      "items": {
+        "properties": {
+          "pages": {
+            "description": "Related Wikipedia article titles",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "text": {
+            "description": "Description of the person",
+            "type": "string"
+          },
+          "year": {
+            "description": "Year of death",
+            "type": "number"
+          }
+        },
+        "required": [
+          "year",
+          "text",
+          "pages"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "events": {
+      "description": "Historical events on this day",
+      "items": {
+        "properties": {
+          "pages": {
+            "description": "Related Wikipedia article titles",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "text": {
+            "description": "Description of the event",
+            "type": "string"
+          },
+          "year": {
+            "description": "Year of the event",
+            "type": "number"
+          }
+        },
+        "required": [
+          "year",
+          "text",
+          "pages"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "holidays": {
+      "description": "Holidays and observances on this day",
+      "items": {
+        "properties": {
+          "pages": {
+            "description": "Related Wikipedia article titles",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "text": {
+            "description": "Description of the holiday",
+            "type": "string"
+          }
+        },
+        "required": [
+          "text",
+          "pages"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "month": {
+      "description": "Two-digit month number provided",
+      "type": "string"
+    }
+  },
+  "required": [
+    "month",
+    "day",
+    "events",
+    "births",
+    "deaths",
+    "holidays"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "day": "20",
+    "month": "07"
+  },
+  {
+    "day": "25",
+    "month": "12"
+  }
+]

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is well-established. The description adds meaningful behavioral context: the types of content returned (events, births, deaths, holidays) and the 'across all years' scope, which informs the user about the tool's comprehensive temporal nature.

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 a single, well-structured sentence that front-loads the action and clearly states the resource and input. There is no redundant or extraneous wording, making it extremely concise and effective.

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?

The tool is simple with only two parameters, and the schema plus annotations already provide substantial context. An output schema exists, so the description does not need to explain return values. The description covers the core scope and content categories, making it fully complete for this low-complexity tool.

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% description coverage, with both 'month' and 'day' parameters clearly documented as two-digit strings with examples. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 function with the verb 'Get' and specifies the resource: historical events, births, deaths, and holidays. It also defines the input scope (a given month and day) and temporal span (across all years), distinguishing it from all sibling tools, none of which offer date-based historical data.

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 clearly conveys when to use the tool: whenever a user needs historical events, births, deaths, or holidays for a specific month and day. It provides a clear context without explicit exclusions, but since no sibling tools share this exact purpose, strong differentiation is not needed.

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

All wikifeed tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.