Dependency Vulnerability Tracker — package security advisories ($0.01/query)

data_session_open

Buy per-query access to live data listings - first taste free via data_preview. Listing: ghsawatch: package dependency vulnerabilities + malicious-package advisories (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.8/5.0

Behavior4/5

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

The description discloses key behaviors: cost per query, max queries per session, buyer_address defaulting to the caller's own wallet, and constraint enforcements on listing reference and field lengths. It also indicates that opening a session is a state-changing, prepaid purchase, consistent with the non-readonly annotation. Some implementation details are included, but they do not obscure the user-facing behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly long and includes substantial implementation details such as pydantic subclassing, type: ignore marks, mypy LSP violations, and internal handler references. While the first sentence is concise, the rest burdens the tool definition with low-level technical notes that an agent likely does not need. It would be much more effective if trimmed to the core usage and behavior.

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?

The description provides necessary context for some parameters and the overall prepaid session flow, but it omits an explanation of the return value or outcome of opening a session (e.g., session ID, open_tx_hash). It also leaves proof_escrow_id unexplained, and the lack of an output schema makes the missing return-value information more significant. The context is adequate for basic use but not fully complete.

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 description adds meaning beyond the schema for listing_slug, listing_id, buyer_address, max_queries, and open_tx_hash by explaining the exactly-one requirement and the buyer_address default. However, proof_escrow_id is not explained at all, and the description does not fully cover all parameters. The schema itself already describes some fields, so the incremental contribution is partial.

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 clearly states the tool's purpose: open a prepaid data session for per-query access to a specific listing, with cost per query and session cap. It distinguishes this from related actions by mentioning the preview-first flow and the subsequent fund/query steps. The verb 'open' and resource 'data session' are explicit.

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 a clear usage sequence: preview via data_preview first, then open a prepaid session, then fund and query. It also notes the REST endpoint distinction and the MCP-only relaxations, which helps an agent know when this tool is the right choice. However, it does not explicitly enumerate when to prefer alternative session-related tools like attach_escrow or fund.

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

All Dependency Vulnerability Tracker — package security advisories ($0.01/query) 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?