Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Wikipedia featured feed

wikipedia_feed_get
Read-onlyIdempotent

Fetch a Wikipedia edition's featured article, most-read articles, picture of the day, and on-this-day entries for a chosen language and date.

Instructions

Get a Wikipedia edition's featured article, most-read articles, picture of the day and on-this-day entries for a day. Optional inputs: lang and date.

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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "wikipedia_feed_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay, `YYYY-MM-DD`. Default: yesterday, UTC.
langNoWikimedia edition code, e.g. `en`, `de`, `ja`, `simple` or `zh-min-nan`. Default: `en`.en
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

B3.2/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 covered elsewhere. The description adds the useful detail that the call returns a bundle of four content sections per day, which matters because there is no output schema. It omits any note on rate limits, caching, or whether an edition/date with no data returns empty sections or an error.

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?

Two short sentences, front-loaded with the resource and its content sections before the optional-input note. The second sentence is mild redundancy against a 100%-covered schema, but it is compact and costs little.

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 read-only, five-parameter tool with full schema coverage and no output schema, listing the returned sections is the main thing an agent needs. It is only slightly short of complete: the shape of the returned feed and the empty-data behavior are left unstated.

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 the schema already documents `lang` formats, the `YYYY-MM-DD` pattern, and the default of yesterday UTC. The description repeats only that `lang` and `date` are optional and ignores the required `context`, `llm_model`, and `conversation_id` parameters. Baseline 3 is appropriate where the schema does the heavy lifting.

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 (Get) and resource (a Wikipedia edition's daily featured feed), and enumerates the four content sections returned: featured article, most-read articles, picture of the day, and on-this-day entries. That enumeration separates it from single-purpose siblings such as wikipedia_onthisday_list, though the description never names those siblings explicitly.

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

Usage Guidelines2/5

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

The only guidance is that `lang` and `date` are optional. Nothing says when to prefer this composite feed over the narrower siblings (wikipedia_onthisday_list, wikipedia_pageviews_top_list) or what the day defaults to in relation to those alternatives. The agent must infer the selection criteria.

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