Agent Margin Router

PyPI Package

pypi_package

Read-only

PyPI project intelligence: latest version, summary, license, author, project URLs, Python requirement, declared dependencies, release count and last release date. Pay per call with USDC or USDT on Base via x402. 3 free calls per wallet.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	PyPI project name.
`wallet`	No	Your EVM wallet address (0x...). Unlocks the free tier (3 free calls per wallet).
`api_key`	No	Optional AMR enterprise API key.
`x_payment`	No	Optional signed x402 payment payload (base64 JSON) for USDC/USDT on Base.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`token`	No	Token actually used for payment (USDC, USDT or FREE).	USDC
`author`	No
`source`	Yes
`yanked`	No
`license`	No
`routing`	Yes	How the request was routed (provider, fallback, cache, latency).
`summary`	No
`homepage`	No
`keywords`	No
`pypi_url`	Yes
`cost_usdc`	Yes	Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.
`fetched_at`	No	UTC timestamp when the data was fetched.
`classifiers`	No
`project_urls`	No
`release_count`	No
`requires_dist`	No
`latest_version`	No
`requires_python`	No
`dependency_count`	No
`freshness_seconds`	Yes	Age of the underlying data in seconds (0 = fetched live).
`latest_released_at`	No
`x_payment_response`	No	Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Response for ``POST /pypi-package``.",
+  "properties": {
+    "author": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Author"
+    },
+    "classifiers": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Classifiers",
+      "type": "array"
+    },
+    "cost_usdc": {
+      "description": "Price charged in stablecoin units (USDC/USDT 1:1); 0 on the free tier.",
+      "title": "Cost Usdc",
+      "type": "number"
+    },
+    "dependency_count": {
+      "default": 0,
+      "title": "Dependency Count",
+      "type": "integer"
+    },
+    "fetched_at": {
+      "description": "UTC timestamp when the data was fetched.",
+      "format": "date-time",
+      "title": "Fetched At",
+      "type": "string"
+    },
+    "freshness_seconds": {
+      "description": "Age of the underlying data in seconds (0 = fetched live).",
+      "title": "Freshness Seconds",
+      "type": "integer"
+    },
+    "homepage": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Homepage"
+    },
+    "keywords": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Keywords"
+    },
+    "latest_released_at": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Latest Released At"
+    },
+    "latest_version": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Latest Version"
+    },
+    "license": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "License"
+    },
+    "name": {
+      "title": "Name",
+      "type": "string"
+    },
+    "project_urls": {
+      "additionalProperties": true,
+      "title": "Project Urls",
+      "type": "object"
+    },
+    "pypi_url": {
+      "title": "Pypi Url",
+      "type": "string"
+    },
+    "release_count": {
+      "default": 0,
+      "title": "Release Count",
+      "type": "integer"
+    },
+    "requires_dist": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Requires Dist",
+      "type": "array"
+    },
+    "requires_python": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Requires Python"
+    },
+    "routing": {
+      "description": "How the request was routed (provider, fallback, cache, latency).",
+      "properties": {
+        "cache_hit": {
+          "default": false,
+          "description": "True if the result was served from cache.",
+          "title": "Cache Hit",
+          "type": "boolean"
+        },
+        "fallback_used": {
+          "default": false,
+          "description": "True if the primary provider failed and a fallback served the result.",
+          "title": "Fallback Used",
+          "type": "boolean"
+        },
+        "latency_ms": {
+          "default": 0,
+          "description": "End-to-end routing latency in milliseconds.",
+          "title": "Latency Ms",
+          "type": "integer"
+        },
+        "provider": {
+          "description": "Name of the upstream provider that served the result.",
+          "title": "Provider",
+          "type": "string"
+        },
+        "providers_tried": {
+          "description": "Providers attempted, in order.",
+          "items": {
+            "type": "string"
+          },
+          "title": "Providers Tried",
+          "type": "array"
+        }
+      },
+      "required": [
+        "provider"
+      ],
+      "title": "RoutingMeta",
+      "type": "object"
+    },
+    "source": {
+      "title": "Source",
+      "type": "string"
+    },
+    "summary": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Summary"
+    },
+    "token": {
+      "default": "USDC",
+      "description": "Token actually used for payment (USDC, USDT or FREE).",
+      "title": "Token",
+      "type": "string"
+    },
+    "x_payment_response": {
+      "description": "Base64-encoded x402 settlement receipt (mirrors the X-PAYMENT-RESPONSE header). Only present when the call was paid with `x_payment`.",
+      "type": "string"
+    },
+    "yanked": {
+      "default": false,
+      "title": "Yanked",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "freshness_seconds",
+    "cost_usdc",
+    "routing",
+    "name",
+    "pypi_url",
+    "source"
+  ],
+  "type": "object"
+}

AddedSep 13, 2026

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 and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral context: it is a paid API with a free tier (3 free calls per wallet), payment via USDC/USDT on Base through x402, and it returns a defined set of project intelligence fields. This goes beyond the annotations by explaining the commercial/rate-limit behavior.

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?

The description is two sentences: the first packs the core purpose and data points, the second covers payment. It is front-loaded with the most important information. The list of data points is slightly long but earns its place by clarifying the tool's scope. No wasted words.

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

Completeness4/5

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

Given the output schema exists and the annotations cover read-only/open-world behavior, the description is largely complete. It explains the payment model, which is essential for an agent to know before invoking. It could mention that the wallet is optional for the free tier, but the schema already covers that. The only minor gap is not stating what happens if no wallet is provided (likely paid), but the payment sentence implies it.

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 the schema already documents all four parameters. The description adds context about the wallet unlocking the free tier and the x402 payment payload, which complements the schema. However, it doesn't add much beyond what the schema descriptions already state, so a baseline 3 is appropriate.

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 opens with a clear verb and resource: 'PyPI project intelligence' followed by a specific list of data points (latest version, summary, license, author, project URLs, Python requirement, declared dependencies, release count, last release date). This distinguishes it from siblings like npm_package and github_repo_summary by naming the exact package registry and the kind of intelligence returned.

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 implies when to use it: when you need PyPI project metadata. It does not explicitly name alternatives or exclusions, but the sibling list makes the domain clear (e.g., npm_package for npm). The payment note also gives context for when wallet/api_key parameters are needed, which is useful usage guidance.

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

All Agent Margin Router tools Inspect

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.