Skip to main content
Glama

wikiviews

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Get Top Articles

get_top_articles
Read-onlyIdempotent

Get the most viewed Wikipedia articles for a specific day. Returns up to 1000 articles ranked by view count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesDay as zero-padded 2-digit string (e.g. "15")
yearYesYear as 4-digit string (e.g. "2024")
monthYesMonth as zero-padded 2-digit string (e.g. "01")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
countYesNumber of top articles returned
articlesYesTop viewed articles for the day

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "description": "Top viewed articles for the day",
+      "items": {
+        "properties": {
+          "article": {
+            "description": "Article title with underscores replaced by spaces",
+            "type": "string"
+          },
+          "rank": {
+            "description": "Article rank by view count",
+            "type": "number"
+          },
+          "views": {
+            "description": "Number of pageviews",
+            "type": "number"
+          }
+        },
+        "required": [
+          "rank",
+          "article",
+          "views"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of top articles returned",
+      "type": "number"
+    },
+    "date": {
+      "description": "Date in YYYY-MM-DD format",
+      "type": "string"
+    }
+  },
+  "required": [
+    "date",
+    "count",
+    "articles"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "day": "15",
+    "month": "01",
+    "year": "2024"
+  },
+  {
+    "day": "25",
+    "month": "12",
+    "year": "2023"
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The description adds behavioral context beyond the annotations by stating a return limit of up to 1000 articles and ranking by view count, which is not disclosed in the annotations. It also implies read-only behavior consistent with readOnlyHint. No contradictions noted.

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 one succinct sentence that immediately states the core function and key output characteristics. It is front-loaded with the action and resource, with no filler or redundant information.

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?

Given the simplicity of the tool, the presence of a rich input schema, and comprehensive annotations, the description covers the necessary context: what is retrieved (most viewed articles), the temporal scope (specific day), and an important output detail (limit of 1000). The describing of the output is sufficient despite the existence of an output schema, as it does not over-explain.

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?

Since the schema already provides descriptions for all three parameters (year, month, day) with 100% coverage, the description doesn't need to add parameter details. It does reinforce that the date parameters target a 'specific day', but this is minor added value. Baseline 3 is appropriate.

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 it gets the most viewed Wikipedia articles for a specific day, using the specific verb 'Get' and resource 'most viewed Wikipedia articles'. It distinguishes itself from sibling tools like get_article_views, which focus on individual article view counts, and get_project_views, which focus on project-level data.

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 clear context: use this tool when you need the top articles for a specific day. It does not explicitly name alternatives or exclusions, but the specificity of 'most viewed' and 'for a specific day' strongly implies its niche. The sibling list further clarifies distinctions, though not referenced.

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

All wikiviews 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