Skip to main content
Glama

Wikifeed

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Featured Article

featured_article
Read-onlyIdempotent

Get Wikipedia's featured article for a specific date.

Input Schema

NameRequiredDescriptionDefault
dayYesTwo-digit day number (e.g., "01", "15")
yearYesFour-digit year (e.g., "2024")
monthYesTwo-digit month number (e.g., "01", "12")

Output Schema

NameRequiredDescriptionDefault
urlYesWikipedia page URL or null
imageYesFeatured image or null
titleYesWikipedia article title
extractYesExtract or summary of the article
descriptionYesShort description or null
display_titleYesFormatted display title of the article

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "description": {
+      "description": "Short description or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "display_title": {
+      "description": "Formatted display title of the article",
+      "type": "string"
+    },
+    "extract": {
+      "description": "Extract or summary of the article",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "image": {
+      "description": "Featured image or null",
+      "properties": {
+        "height": {
+          "description": "Image height in pixels",
+          "type": "number"
+        },
+        "source": {
+          "description": "Image URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Image width in pixels",
+          "type": "number"
+        }
+      },
+      "required": [
+        "source",
+        "width",
+        "height"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Wikipedia article title",
+      "type": "string"
+    },
+    "url": {
+      "description": "Wikipedia page URL or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "title",
+    "display_title",
+    "description",
+    "extract",
+    "url",
+    "image"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "day": "15",
+    "month": "01",
+    "year": "2024"
+  },
+  {
+    "day": "04",
+    "month": "07",
+    "year": "2023"
+  }
+]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

The description adds the date-scoping constraint but does not disclose additional behavior such as output format or error handling. The annotations already cover read-only and non-destructive hints, so the bar is lower, and the description adds some context beyond the 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 a single, succinct sentence with no filler words. It conveys all necessary information efficiently.

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 simple, with complete schema descriptions and an output schema. The description is adequate for this simplicity, though it could mention that the date is required, but that is already 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%, with each parameter described. The description adds no extra parameter semantics beyond stating 'specific date', which is already implied by the 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?

The description clearly states the action 'Get' and the target resource 'Wikipedia's featured article' with a specific date scope. This distinguishes it from siblings like 'on_this_day' or 'picture_of_day'.

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 clearly implies usage: when you need Wikipedia's featured article for a specific date, use this tool. However, it does not explicitly mention alternatives or when not to use it.

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

All Wikifeed toolsInspect
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.

Resources