Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Python package facts from PyPI in one call: latest version, summary, required Python, license, project URLs, number of r

pypi_package
Read-onlyIdempotent

Python package facts from PyPI in one call: latest version, summary, required Python, license, project URLs, number of releases, latest upload (name=requests). For dependency and supply-chain agents. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pypi_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNopackage name, e.g. requests
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/open-world, and the description adds the material facts they cannot: a $0.002 USDC charge per call on Base via x402, and that all facts arrive 'in one call' (no pagination). The first-call payment handshake is left to the schema rather than explained here.

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?

A single dense sentence that front-loads the field list, with no filler. The trailing '(name=requests)' example and the duplicated title text make it slightly awkward but not wasteful.

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?

With no output schema, enumerating the returned fields is exactly what an agent needs, and the cost/payment model is disclosed. Little an agent needs to call this correctly is missing.

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 description coverage is 100%, so both parameters are already documented, including the x402 payment flow. The description only restates the 'name=requests' example already present in the schema, adding no new parameter semantics.

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 resource (PyPI package) and enumerates the returned facts — latest version, summary, required Python, license, project URLs, release count, latest upload. The 'from PyPI' scoping implicitly separates it from npm_package, but no sibling is named explicitly.

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?

Guidance is limited to an audience tag ('For dependency and supply-chain agents'), which implies usage without stating when to call this versus alternatives like npm_package. No exclusions or preconditions are given.

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.

Resources