Skip to main content
Glama
Sign In

Onthisday

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Deaths

get_deaths
Read-onlyIdempotent

Find notable people who died on a specific date. Provide month (1-12) and day (1-31). Returns names, death years, and biographical detail.

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": 14,
      "month": 4
    },
    "name": "get_deaths"
  }
}

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 deaths found
deathsYesArray of notable deaths

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of deaths found",
+      "type": "number"
+    },
+    "date": {
+      "description": "The date string from the API response",
+      "type": "string"
+    },
+    "deaths": {
+      "description": "Array of notable deaths",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Person's name and biographical details",
+            "type": "string"
+          },
+          "wikipedia": {
+            "description": "Wikipedia references for the person",
+            "items": {
+              "properties": {
+                "title": {
+                  "description": "Wikipedia article title",
+                  "type": "string"
+                },
+                "url": {
+                  "description": "Wikipedia article URL",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "year": {
+            "description": "Year the person died",
+            "type": "string"
+          }
+        },
+        "required": [
+          "year",
+          "description",
+          "wikipedia"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "type": {
+      "description": "The type of entries returned",
+      "enum": [
+        "deaths"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "type",
+    "count",
+    "deaths"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "day": 14,
+    "month": 4
+  },
+  {
+    "day": 31,
+    "month": 8
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the scope 'notable people' and mentions return content, but with an output schema present, this adds minimal behavioral context beyond what annotations and schema provide.

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 two concise sentences, front-loaded with the core purpose, with no wasted words.

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 simple two-parameter lookup with comprehensive annotations and an output schema, the description adequately covers the tool's purpose and input expectations. No additional context is necessary.

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 coverage is 100% with both day and month described in the input schema. The description reinforces the format (1-12, 1-31) but does not add meaning beyond the schema.

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 the specific verb 'Find' and clearly identifies the resource as 'notable people who died on a specific date.' This distinguishes it from sibling tools like get_births and get_events by focusing on death and date.

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 provides clear context for use (providing a month and day to get deaths), but does not explicitly mention alternatives or when not to use this tool. It implies usage by stating the required inputs.

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