Skip to main content
Glama

wikifeed

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Picture Of Day

picture_of_day
Read-onlyIdempotent

Get Wikipedia's picture of the day for a specific date, including title, description, and image URL.

Input Schema

TableJSON 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

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTitle of the picture
file_pageYesFile page URL or null
image_urlYesFull-size image URL or null
thumbnailYesThumbnail image or null
descriptionYesDescription text or null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "description": {
+      "description": "Description text or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "file_page": {
+      "description": "File page URL or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "image_url": {
+      "description": "Full-size image URL or null",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "thumbnail": {
+      "description": "Thumbnail image or null",
+      "properties": {
+        "height": {
+          "description": "Thumbnail height in pixels",
+          "type": "number"
+        },
+        "source": {
+          "description": "Thumbnail URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Thumbnail width in pixels",
+          "type": "number"
+        }
+      },
+      "required": [
+        "source",
+        "width",
+        "height"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Title of the picture",
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "description",
+    "image_url",
+    "thumbnail",
+    "file_page"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "day": "21",
+    "month": "06",
+    "year": "2024"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds valuable behavioral context by specifying the return contents (title, description, image URL) and the date-scoped nature of the retrieval, going beyond what annotations provide.

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, concise sentence that gets straight to the point. It front-loads the main action ('Get Wikipedia's picture of the day') and adds necessary details without filler. Every sentence (and word) earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 3-parameter retrieval tool, the description is complete. It explains what the tool does, what it returns, and the input scope (specific date). Output schema exists, and annotations cover safety. No critical information is missing.

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 (year, month, day) clearly described. The description does not add syntax details beyond what the schema provides, so the baseline score of 3 is appropriate. It reinforces the date concept but doesn't enhance parameter understanding.

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's purpose: 'Get Wikipedia's picture of the day for a specific date'. It uses a specific verb ('Get'), identifies the resource ('Wikipedia's picture of the day'), and mentions the return contents (title, description, image URL). This distinguishes it from siblings like featured_article or on_this_day.

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 context is implied: the tool retrieves a picture based on a specific date, but there is no explicit guidance on when to use it versus alternatives or exclusions. Sibling tools like featured_article are clearly different by name, but the description doesn't mention them or provide when-to-use/when-not-to-use guidance.

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