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 or wallet. Existing source and input limits apply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes
requestIdNoOptional legacy field; ignored in free mode.
maxPriceMicroUsdNoOptional legacy field; ignored in free mode.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
entriesYes
rankingYes
languageYes
sourceUrlYes
retrievedAtYes
namespaceFilterYes
availableEntriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. 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"
+]
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description adds the free-tier context, but 'Existing source and input limits apply' is vague and no rate-limit, pagination, or data-source freshness detail is disclosed.

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

Conciseness4/5

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

Front-loads the capability before the pricing note, and every sentence is reasonably short with little waste. The pricing/legacy caveats could be tightened but do not bloat the description.

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 described, and annotations carry the safety profile. Still, the vague 'source and input limits' and the unexplained namespace-filtering claim leave open questions for a data-fetch tool with a nested required input object.

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?

The description references 'namespace filtering' and 'rank/view counts' that do not correspond to any schema parameter, while the actual parameters (date, limit, language) are left unexplained. With schema coverage at only 67%, the description neither documents the real parameters nor compensates for the gap, and introduces concepts absent from the schema.

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 (return Wikipedia article links ranked by daily pageviews) and names distinguishing traits like official ranking and original rank/view counts, which separates it from siblings such as web_wikipedia_read and web_wikipedia_pack. However, 'namespace filtering' is mentioned even though no namespace parameter exists in the schema, adding slight ambiguity.

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?

Signals the operating context ('FREE during validation. No key, credits or wallet. Existing source and input limits apply'), which tells the agent when this tool is cost-free. But it never names an alternative (e.g., web_wikipedia_read for article bodies) or states when NOT to use this tool, leaving selection between siblings to inference.

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