Skip to main content
Glama
Sign In
wikimedia

wikimedia

by RapidMCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

get_featured

Retrieve featured Wikimedia content including the featured article, most read pages, and picture of the day for a specified date or today.

Instructions

Get featured Wikimedia content for a date. Returns featured article, most read pages, and picture of the day. Parameters: date (YYYY/MM/DD, default today), project ('wikipedia' only), language (en/de/fr/es/ru/ja/zh)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_featured"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
projectNowikipedia
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided. Description specifies output (featured article, most read, picture of the day) and parameter defaults, but does not disclose behavior for invalid dates, rate limits, or whether the operation is read-only. Adequate but not detailed.

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?

Two sentences, concise and no wasted words. Front-loaded with main action and immediately lists parameters.

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 simple retrieval tool with no output schema or annotations, description covers return items and parameters well. Missing error handling details, but completeness is high given complexity.

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

Parameters4/5

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

Input schema has 0% description coverage. Description compensates by specifying date format (YYYY/MM/DD), default values, allowed values for project ('wikipedia' only) and language (list of codes). Adds significant meaning beyond 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?

Description clearly states the tool gets featured Wikimedia content for a date, listing specific items returned (featured article, most read pages, picture of the day). It distinguishes from siblings like get_page (single page) and search_content (search results) by specifying the type of content.

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?

Description does not explicitly state when to use this tool versus alternatives. It implies usage for retrieving featured content by date, but no when-not-to or comparison to sibling tools like get_languages or get_on_this_day.

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