Wikimedia Rest

Featured

featured

Read-onlyIdempotent

Wikipedia's "today's featured" content for a specific date — featured article, most-read, picture of the day, on-this-day events. Use for "what's on Wikipedia today", "featured article on 2026-05-21", or to seed daily-roundup content.

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": 15,
      "year": 2024,
      "month": 3
    },
    "name": "featured"
  }
}

Input Schema

Name	Required	Description	Default
`day`	Yes
`lang`	No
`year`	Yes
`month`	Yes
`project`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds value by specifying the exact content components returned (featured article, most-read, picture of the day, on-this-day events), giving a concrete sense of the tool's output without contradicting annotations.

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 sentences with no filler. The first sentence defines the tool's purpose and scope, and the second offers concrete use cases. It is front-loaded and every word earns its place.

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?

The tool is read-only and has a strong output schema, so the description need not explain return values. It adequately conveys purpose and usage, but the lack of parameter explanations for lang/project means the description is not fully self-sufficient for a 5-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only references the date components ('specific date') without explaining the purpose of lang or project. The parameter names and examples provide some hints, but the description does not compensate for the lack of schema descriptions, leaving the agent to infer the semantics of language and project parameters.

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 returns Wikipedia's 'today's featured' content for a specific date, enumerating the content types (featured article, most-read, picture of the day, on-this-day events). This distinguishes it from siblings like onthisday and random, which focus on narrower scopes.

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 explicit use cases: 'what's on Wikipedia today', 'featured article on 2026-05-21', and 'to seed daily-roundup content'. It gives clear context for when to invoke the tool, though it does not mention exclusions or alternatives.

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

All Wikimedia Rest tools Inspect

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.