Skip to main content
Glama

wikiviews

by io.github.pipeworx-io

Get Project Views

get_project_views
Read-onlyIdempotent

Get aggregate daily pageview totals for all of English Wikipedia over a date range. Dates must be in YYYYMMDD format.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd date in YYYYMMDD format (e.g. "20240131")
startYesStart date in YYYYMMDD format (e.g. "20240101")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd date in YYYYMMDD format
dailyYesDaily pageview breakdown
startYesStart date in YYYYMMDD format
projectYesProject identifier
total_viewsYesTotal pageviews for English Wikipedia

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "daily": {
+      "description": "Daily pageview breakdown",
+      "items": {
+        "properties": {
+          "date": {
+            "description": "Date in YYYYMMDD format",
+            "type": "string"
+          },
+          "views": {
+            "description": "Pageviews for that day",
+            "type": "number"
+          }
+        },
+        "required": [
+          "date",
+          "views"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "end": {
+      "description": "End date in YYYYMMDD format",
+      "type": "string"
+    },
+    "project": {
+      "description": "Project identifier",
+      "type": "string"
+    },
+    "start": {
+      "description": "Start date in YYYYMMDD format",
+      "type": "string"
+    },
+    "total_views": {
+      "description": "Total pageviews for English Wikipedia",
+      "type": "number"
+    }
+  },
+  "required": [
+    "project",
+    "start",
+    "end",
+    "total_views",
+    "daily"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end": "20240131",
+    "start": "20240101"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds only a date format reminder already present in the schema, with no additional behavioral context such as rate limits or edge cases. No contradiction with 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, front-loaded sentence that conveys purpose, scope, and a key constraint without any superfluous words.

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 two-parameter tool with full schema descriptions, rich annotations, and an existing output schema, the one-sentence description is complete. It covers what the tool does and its scope without needing to explain return values.

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?

Input schema coverage is 100% and both parameters have descriptive text with examples. The description only reiterates the YYYYMMDD format, adding no new meaning beyond what the schema already provides.

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'), the resource ('aggregate daily pageview totals for all of English Wikipedia'), and the scope ('over a date range'). This distinguishes it from sibling tools like get_article_views, which focus on specific articles.

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 makes clear that this tool is for site-wide pageview totals for English Wikipedia, implying it should be used when project-level data is needed. However, it does not explicitly name alternatives or provide exclusions, so it falls short of a perfect score.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Every tool has a clearly distinct purpose, from Wikipedia page views to AI visibility checks, entity resolution, and Polymarket betting. No two tools appear overlapping in functionality; descriptions further clarify each tool's unique role.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., get_article_views, subscribe, resolve_entity). No mixing of conventions, and names are descriptive enough to infer purpose.

Tool Count2/5

With 33 tools, the server is overloaded for its name 'wikiviews', which suggests a focused Wikipedia views tool. The set includes unrelated functionality like Polymarket arbitrage, memory storage, and Pipeworx data queries, making the scope feel excessive.

Completeness2/5

For the core domain of Wikipedia views, only 3 tools exist (get_article_views, get_project_views, get_top_articles), missing basic operations like list_articles_per_day. The unrelated tools are extensive, but the server's stated purpose is poorly served.

Resources