Skip to main content
Glama

Agent Utilities Hosted

by dev.workers.agent-utilities.agent-utilities
OverviewDiscussionsAdmin

web_wikipedia_popular

Read-only

Return dated Wikipedia article links ranked by official daily pageviews, with namespace filtering and original rank/view counts. FREE during validation. No key, credits, wallet or preparation needed. Supply your task in input. Existing source and input limits apply.

Input Schema

NameRequiredDescriptionDefault
inputYes

Output Schema

NameRequiredDescriptionDefault
dateYes
entriesYes
rankingYes
languageYes
sourceUrlYes
retrievedAtYes
namespaceFilterYes
availableEntriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / maxPriceMicroUsd
      Removed value: -{
-  "description": "Optional legacy field; ignored in free mode.",
-  "minimum": 0,
-  "type": "integer"
-}
    • removedInput schema / properties / requestId
      Removed value: -{
-  "description": "Optional legacy field; ignored in free mode.",
-  "type": "string"
-}
  2. Changed5 schema fields changed
    • changedInput schema / properties / maxPriceMicroUsd / description
      Previous value: -"Explicit maximum new debit; 0 means recovery only."New value: +"Optional legacy field; ignored in free mode."
    • removedInput schema / properties / maxPriceMicroUsd / maximum
      Removed value: -999999999999
    • changedInput schema / properties / requestId / description
      Previous value: -"Persist the ID returned by agent_utilities_prepare. Reuse after uncertainty."New value: +"Optional legacy field; ignored in free mode."
    • removedInput schema / properties / requestId / pattern
      Removed value: -"^\\d{13}_[A-Za-z0-9_-]{16,80}$"
    • changedInput schema / required
      Previous value: -[
-  "input",
-  "requestId",
-  "maxPriceMicroUsd"
-]New value: +[
+  "input"
+]
  3. Changed2 schema fields changed
    • addedOutput schema / properties / namespaceFilter
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "mainPage": {
+      "type": "string"
+    },
+    "retrievedAt": {
+      "type": "string"
+    },
+    "sourceUrl": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "sourceUrl",
+    "retrievedAt",
+    "mainPage"
+  ],
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "sourceUrl",
-  "date",
-  "language",
-  "retrievedAt",
-  "ranking",
-  "entries",
-  "availableEntries"
-]New value: +[
+  "sourceUrl",
+  "date",
+  "language",
+  "retrievedAt",
+  "namespaceFilter",
+  "ranking",
+  "entries",
+  "availableEntries"
+]
  4. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world profile, and the description adds genuinely useful context they cannot: no API key or wallet required, free during validation, and that source/input limits apply. It stops short of quantifying those limits or describing result pagination, but the auth/cost disclosure is real added value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose clause is front-loaded and efficient, but 'Supply your task in input' and 'Existing source and input limits apply' are vague boilerplate that consume space without adding meaning.

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

Completeness3/5

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

An output schema exists, so return values need not be explained, and the safety profile is covered by annotations. However, for a tool whose only parameter is an undescribed nested object, the description should clarify date format, limit behavior, and language selection; those gaps remain.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter is a nested object, so the description carries the full burden. It only alludes to 'dated' results and 'namespace filtering' without naming the date format, the limit maximum of 100, or the language enum, leaving the actual input semantics to the schema's bare types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: returning dated Wikipedia article links ranked by official daily pageviews, with rank and view counts. This clearly distinguishes it from sibling readers like web_wikipedia_read and web_wikipedia_pack, though it never names those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives cost/prerequisite information (free, no key or credits) but no guidance on when to choose this over web_wikipedia_read, web_wikipedia_pack, or the trial variants. 'Supply your task in input' is not actionable routing guidance.

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

All Agent Utilities Hosted 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