Skip to main content
Glama

Most Read

most_read
Read-onlyIdempotent

Get the most-read English Wikipedia articles (rank, views) for a specific date. Lists publish about a day late: recent dates return found:false with a message; use a date two or more days back.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "day": "01",
      "year": "2024",
      "month": "03"
    },
    "name": "most_read"
  }
}

Input 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

NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
articlesYesTop 20 most-read articles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "articles": {
      +      "description": "Top 20 most-read articles",
      +      "items": {
      +        "properties": {
      +          "description": {
      +            "description": "Short description or null",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "display_title": {
      +            "description": "Formatted display title",
      +            "type": "string"
      +          },
      +          "rank": {
      +            "description": "Ranking position",
      +            "type": "number"
      +          },
      +          "title": {
      +            "description": "Wikipedia article title",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Wikipedia page URL or null",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "views": {
      +            "description": "Number of views",
      +            "type": "number"
      +          }
      +        },
      +        "required": [
      +          "rank",
      +          "title",
      +          "display_title",
      +          "views",
      +          "description",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "date": {
      +      "description": "Date in YYYY-MM-DD format",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "date",
      +    "articles"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "day": "01",
      +    "month": "03",
      +    "year": "2024"
      +  }
      +]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds the important non-obvious behavior that lists publish about a day late and that recent dates return found:false with a message, which materially helps an agent avoid a bad call.

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 two tightly written sentences with no wasted text. The purpose is front-loaded and the operational caveat follows immediately.

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 simple three-parameter schema, the existing output schema, and the safety annotations, the description provides all invocation-critical context: what it returns, the date scope, and the recent-date failure behavior.

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

Parameters4/5

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

Schema description coverage is 100%, so the day/month/year formats are already documented in the schema. The description adds a meaningful semantic restriction on the date parameters by specifying that the date should be two or more days back.

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?

It states a specific verb, resource, scope, and return fields: get most-read English Wikipedia articles with rank and views for a specific date. This clearly distinguishes it from sibling Wikipedia date tools such as featured_article or picture_of_day.

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 gives clear contextual guidance by saying the tool is for a specific date and explicitly instructing the agent to use a date two or more days back. It does not name alternatives or say when not to use it, but the usage constraint is concrete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.