Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch)

data_session_open

Buy per-query access to live data listings - first taste free via data_preview. Listing: techlaunchwatch: Agent Tool Releases & Tech Announcements (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.9/5.0

Behavior4/5

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

Annotations are only generic hints, so the description carries the behavioral burden. It discloses the cost per query, the 20-query session cap, and the prepaid nature, which are material traits for an agent deciding whether to invoke a paid tool. It does not cover transaction mechanics, but adds meaningful context beyond the annotations.

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?

Three short sentences with the core purpose front-loaded and no filler. The specific listing detail is useful but somewhat domain-specific, which makes the description slightly less transferable across listings.

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

Completeness2/5

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

For a paid, six-parameter tool with no output schema, the description omits what a successful call returns (e.g., a session id), does not clarify open_tx_hash or proof_escrow_id roles, and does not state prerequisites. The workflow hint helps, but an agent would need to inspect the schema and siblings to reliably complete the call.

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 input schema already covers listing_id, listing_slug, and buyer_address semantics, and the global schema note explains the slug-or-UUID rule and wallet default. The tool description adds the price and max-query session cap, but leaves open_tx_hash and proof_escrow_id semantically unexplained, and schema coverage is only 50%.

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?

States the action as 'Buy per-query access' and 'Open a prepaid session', naming the exact resource and even a concrete listing with price. It clearly distinguishes itself from data_preview by positioning this as the paid path after a free taste.

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 places the tool in a workflow: try data_preview first, then open a prepaid session, then fund and query. It names one alternative and gives clear selection context, though it does not exhaustively enumerate when-not conditions or all sibling tools.

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

All Agent Tool Release Tracker — buy per-query in-session (techlaunchwatch) 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?