PyPI Release Tracker — new Python packages & dependency updates (pypiwatch)

data_session_open

Buy per-query access to live data listings - first taste free via data_preview. Listing: pypiwatch: New PyPI package releases & Python dependency updates (0.01 USDC/query (max 20 queries/session)). Open a prepaid session, then fund and query.

Input Schema

TableJSON Schema

Name	Required	Description
`listing_id`	No	UUID of the listing. Provide exactly one of listing_slug or listing_id.
`max_queries`	No
`listing_slug`	No	Public listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.
`open_tx_hash`	No
`buyer_address`	No	Buyer EVM address. Optional: defaults to your own platform wallet when omitted.
`proof_escrow_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedSep 7, 2026

addedInput schema / description

Added value: +"MCP-only input for ``data_session_open``.\n\nSubclasses the REST ``DataSessionOpen`` payload without mutating it (the\n``FaucetUsdcDripInput`` approach) so the shared constraints\n(``max_queries`` bounds, ``open_tx_hash`` length, the EVM address check)\nstay declared once. Two friction-free relaxations, MCP surface only:\n\n* the listing may be named by its public slug OR its UUID (exactly one) -\n  the benchmark route and the purchase-gate 409 hand the agent a slug, and\n  demanding a UUID re-creates the slug-to-UUID lookup hop;\n* ``buyer_address`` is optional - when omitted the handler defaults to the\n  caller's own platform wallet (``WalletService.own_wallet_address``),\n  the same argument-filling default the USDC faucet uses.\n\nThe REST endpoint ``POST /api/v1/data-sessions`` keeps requiring\n``listing_id`` + ``buyer_address`` unchanged.\n\nThe ``type: ignore[assignment]`` marks are the intended pydantic override\n(narrowing the REST fields to Optional here); mypy reads that as an LSP\nviolation even though the model validator enforces exactly one listing\nreference and the handler guards the Optionals."

addedInput schema / properties / buyer_address / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / buyer_address / default
```
Added value: +null
```

addedInput schema / properties / buyer_address / description

Added value: +"Buyer EVM address. Optional: defaults to your own platform wallet when omitted."

removedInput schema / properties / buyer_address / type
```
Removed value: -"string"
```

addedInput schema / properties / listing_id / anyOf

Added value: +[
+  {
+    "format": "uuid",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / listing_id / default
```
Added value: +null
```

addedInput schema / properties / listing_id / description

Added value: +"UUID of the listing. Provide exactly one of listing_slug or listing_id."

removedInput schema / properties / listing_id / format
```
Removed value: -"uuid"
```
removedInput schema / properties / listing_id / type
```
Removed value: -"string"
```

addedInput schema / properties / listing_slug

Added value: +{
+  "anyOf": [
+    {
+      "minLength": 1,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Public listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.",
+  "title": "Listing Slug"
+}

removedInput schema / required

Removed value: -[
-  "listing_id",
-  "buyer_address"
-]

changedInput schema / title

Previous value: -"DataSessionOpen"New value: +"DataSessionOpenInput"

First observedSep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations only state readOnly=false, idempotent=false, and destructive=false. The description adds meaningful context: this is a paid access path, costs 0.01 USDC/query, has a 20-query session cap, and needs funding before querying. However, it does not clarify whether opening the session itself costs money, whether sessions expire, or what side effects occur, so the behavioral picture is incomplete.

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 compact and front-loads the core purpose before adding listing and workflow details. It earns its sentences with pricing, the free-preview alternative, and the fund-then-query sequence. The phrase 'prepaid session, then fund and query' is slightly ambiguous, but the overall structure is efficient.

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?

There is no output schema, and the description does not explicitly say what is returned (e.g., a session ID to pass to data_session_fund or data_session_query). Advanced parameters like open_tx_hash and proof_escrow_id remain unexplained. The workflow hint and schema-level notes about exactly-one listing reference and buyer_address default help, but for a payment-related mutation tool this still leaves meaningful gaps.

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?

The schema already documents listing_id, listing_slug, and buyer_address. The description adds a concrete listing slug value ('pypiwatch') and a listing-specific max-query cap (20), which is useful for max_queries. It says nothing about open_tx_hash or proof_escrow_id, and with only 50% schema coverage the tool description only partially compensates for those undocumented params.

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?

The description clearly identifies the action as opening/buying per-query access to a live data listing, and it names the concrete listing (pypiwatch) with pricing. It also distinguishes itself from data_preview by calling that the free first taste. The slight mismatch between 'Buy per-query access' and 'Open a prepaid session' keeps it from being perfectly crisp, but the core resource and verb are evident.

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?

It points users to data_preview for the free first taste and gives the post-open workflow: 'then fund and query,' which maps to the sibling tools data_session_fund and data_session_query. This is useful routing guidance, though it does not explicitly state when not to use this tool beyond the free-preview hint.

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

All PyPI Release Tracker — new Python packages & dependency updates (pypiwatch) 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.

Resources

Need Help?