Skip to main content
Glama

onthisday

by io.github.pipeworx-io
OverviewAdmin

Get Births

get_births
Read-onlyIdempotent

Find notable people born on a specific date. Provide month (1-12) and day (1-31). Returns names, birth years, and biographical details.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesThe date string from the API response
typeYesThe type of entries returned
countYesNumber of births found
birthsYesArray of notable births

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "births": {
+      "description": "Array of notable births",
+      "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 was born",
+            "type": "string"
+          }
+        },
+        "required": [
+          "year",
+          "description",
+          "wikipedia"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of births found",
+      "type": "number"
+    },
+    "date": {
+      "description": "The date string from the API response",
+      "type": "string"
+    },
+    "type": {
+      "description": "The type of entries returned",
+      "enum": [
+        "births"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "type",
+    "count",
+    "births"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "day": 15,
+    "month": 1
+  },
+  {
+    "day": 9,
+    "month": 10
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool read-only, open-world, idempotent, and non-destructive, so the bar is lower. The description adds behavioral context by specifying the output includes names, birth years, and biographical details, which goes beyond the annotations and helps the agent understand what to expect.

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 only two sentences, front-loaded with the purpose and then the required inputs. Every sentence adds information, and there is no redundant or extraneous text.

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 tool with a rich output schema and strong annotations, the description is adequately complete. It covers what the tool does, what inputs are needed, and what users can expect in the output, making it sufficient for a straightforward query 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?

Schema coverage is 100% with descriptive property definitions for month and day. The description restates the same ranges (1-12, 1-31) without adding new semantic value beyond the schema, so the baseline 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 finds notable people born on a specific date, using the verb 'Find' with a specific resource. It distinguishes from sibling tools like get_deaths and get_events by focusing on births and listing the specific return data (names, birth years, biological details).

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 usage context: the tool is for finding births on a specific date, requiring month and day. It does not explicitly compare to alternatives or state exclusions, but the context is sufficiently clear to guide appropriate use.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources