Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia on-this-day entries

wikipedia_onthisday_list
Read-onlyIdempotent

Retrieve Wikipedia anniversaries, births, deaths, events, or holidays for a specific month and day. Provide month and day to get a curated list of historical data.

Instructions

Get selected Wikipedia anniversaries, births, deaths, events or holidays for a month and day. Requires month and day. Returns a list.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "month": "<month>",
      "day": "<day>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_onthisday_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesRequired. Day of the month, 1 to 31.
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
typeNo`selected`, `births`, `deaths`, `events`, `holidays` or `all` (default). Each type can be several MB, and `all` returns every type at once.all
monthYesRequired. Month, 1 to 12.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only 'Returns a list' plus the required-parameter note; it omits behavior disclosed elsewhere in the schema, notably that each type can be several MB and that `all` returns everything at once, which is the most consequential behavior for a caller.

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?

Three short sentences, front-loaded with purpose, then prerequisites, then return shape. No filler, no redundancy with itself.

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 7-parameter read tool with no output schema, the description covers purpose, required inputs and the return type, and the schema fills in the unusual analytics/conversation parameters. A minor gap is the absence of any note about response size or the conversation_id sequencing requirement, though both are stated in the schema.

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 every parameter (day, month, lang, type, context, llm_model, conversation_id) is already documented in the schema, including enum values and defaults. The description merely restates that month and day are required and does not add format or semantic detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb and resource ('Get selected Wikipedia anniversaries, births, deaths, events or holidays for a month and day') and echoes the enum categories from the schema, so an agent can tell it apart from the other wikipedia_* siblings. It stops short of naming a contrasting alternative, so a 4 rather than a 5.

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 only implied: the phrasing 'for a month and day' plus 'Requires `month` and `day`' tells the agent the necessary inputs, but there is no explicit when-to-use versus when-not, and no pointer to sibling tools such as wikipedia_feed_get. Adequate but leaves routing inference to the agent.

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

Deploy Server

Other Tools