Skip to main content
Glama
Sign In

Pypi Stats

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Python Major

python_major
Read-onlyIdempotent

Fetch PyPI download breakdown for a package by Python major version (2 vs 3) from pypistats.org. Returns per-version download counts.

Input Schema

NameRequiredDescriptionDefault
packageYes

Output Schema

NameRequiredDescriptionDefault
dataNoDownloads by Python major version
typeNoResponse type
packageNoPackage name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "package": "flask"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Downloads by Python major version",
+      "items": {
+        "properties": {
+          "category": {
+            "description": "Python major version",
+            "type": "string"
+          },
+          "downloads": {
+            "description": "Number of downloads",
+            "type": "integer"
+          },
+          "percent": {
+            "description": "Percentage of total downloads",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "package": {
+      "description": "Package name",
+      "type": "string"
+    },
+    "type": {
+      "description": "Response type",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds that data is sourced from pypistats.org and returns per-version counts, providing useful context beyond 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 sentence that efficiently communicates the tool's purpose and output. No unnecessary words; information is front-loaded.

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 low complexity (one parameter, output schema exists), the description is complete. It explains what the tool does and what it returns. No missing information needed for an agent to invoke it correctly.

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?

Schema coverage is 0%, meaning the schema provides no description for the 'package' parameter. The description only implies it is the package name through the example. With a single required parameter, the meaning is inferred, but the description does not explicitly state format or constraints.

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 explicitly states the action ('Fetch PyPI download breakdown'), the resource ('package by Python major version'), and the data source ('pypistats.org'). It also mentions the return type ('per-version download counts'). This clearly distinguishes from sibling tool 'python_minor' which would handle minor versions.

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?

The description implies usage for major version breakdown, but does not explicitly state when to use this tool over alternatives like 'python_minor'. No when-not-to-use or exclusion criteria are provided.

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

All Pypi Stats toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources