Skip to main content
Glama
Sign In

Onthisday

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Events

get_events
Read-onlyIdempotent

Search historical events on a specific date. Provide month (1-12) and day (1-31). Returns event descriptions, years, and details.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "day": 20,
      "month": 7
    },
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of the month (1-31).
monthYesMonth as a number (1-12).

Output Schema

NameRequiredDescriptionDefault
dateYesThe date string from the API response
typeYesThe type of entries returned
countYesNumber of events found
eventsYesArray of historical events

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / events / items / properties / description / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "day": 20,
+    "month": 7
+  },
+  {
+    "day": 25,
+    "month": 12
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of events found",
+      "type": "number"
+    },
+    "date": {
+      "description": "The date string from the API response",
+      "type": "string"
+    },
+    "events": {
+      "description": "Array of historical events",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Event description",
+            "type": "string"
+          },
+          "wikipedia": {
+            "description": "Wikipedia references for the event",
+            "items": {
+              "properties": {
+                "title": {
+                  "description": "Wikipedia article title",
+                  "type": "string"
+                },
+                "url": {
+                  "description": "Wikipedia article URL",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "year": {
+            "description": "Year the event occurred",
+            "type": "string"
+          }
+        },
+        "required": [
+          "year",
+          "description",
+          "wikipedia"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "description": "The type of entries returned",
+      "enum": [
+        "events"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "type",
+    "count",
+    "events"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "_apiKey": "your-mixpanel-api-key",
-    "event": "Sign Up",
-    "from_date": "2024-01-01",
-    "to_date": "2024-01-31"
-  },
-  {
-    "_apiKey": "your-mixpanel-api-key",
-    "from_date": "2024-02-01",
-    "to_date": "2024-02-29"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "description": "Event data query result from Mixpanel",
-  "type": "object"
-}New value: +null
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Event data query result from Mixpanel",
+  "type": "object"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-mixpanel-api-key",
+    "event": "Sign Up",
+    "from_date": "2024-01-01",
+    "to_date": "2024-01-31"
+  },
+  {
+    "_apiKey": "your-mixpanel-api-key",
+    "from_date": "2024-02-01",
+    "to_date": "2024-02-29"
+  }
+]
  6. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only a light note about the shape of results, and with an output schema present even that is not needed.

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?

Three short sentences, front-loaded with the core action, with no filler. The final sentence about return values is mildly redundant given the output schema exists, which keeps it from being maximally tight.

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?

For a two-parameter read tool with full schema coverage, rich annotations, and an output schema, the description covers what the agent needs to invoke it. The only real omission is sibling differentiation against get_births/get_deaths for the same date-lookup intent.

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?

Schema description coverage is 100%, so both parameters already document their ranges (1-31 and 1-12) and the schema even provides examples. The description merely repeats the same numeric ranges, adding no new syntax, format, or edge-case meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search historical events') scoped to a date, which is unambiguous. However, it does not distinguish itself from close siblings like get_births and get_deaths, which are also 'on this date' lookups, so the agent gets no help choosing among them.

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

Usage Guidelines3/5

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

Usage is implied by 'Search historical events on a specific date' and the instruction to supply month and day, which conveys the calling context. There is no when-not-to-use guidance and no mention of the births/deaths alternatives that could satisfy a similar intent.

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

All Onthisday toolsInspect
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.

Resources