Skip to main content
Glama

Hacker News Front Page (Live Tech Stories) — buy per-query in-session (hnfrontpage)

by com.a2awire
OverviewDiscussionsAdmin

data_session_open

Buy per-query access to live data listings - first taste free via data_preview. Listing: hnfrontpage: Hacker News Front Page (Live) (0.01 USDC/query (max 20 queries/session)). Open a prepaid session, then fund and query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listing_idNoUUID of the listing. Provide exactly one of listing_slug or listing_id.
max_queriesNo
listing_slugNoPublic listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.
open_tx_hashNo
buyer_addressNoBuyer EVM address. Optional: defaults to your own platform wallet when omitted.
proof_escrow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • 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"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The description discloses meaningful behavioral context beyond annotations: this is a paid operation with a specific cost (0.01 USDC/query) and a session cap (max 20 queries/session). It also implies a funding prerequisite and a non-idempotent session-opening action, which is consistent with the idempotentHint=false annotation. No contradiction with annotations is present.

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

Conciseness5/5

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

The description is compact and front-loaded with the core purpose ('Buy per-query access'). It packs actionable details—pricing, listing identifier, session limit, and free preview alternative—into two sentences without verbose filler.

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?

For a paid session-opening tool with no output schema and several optional parameters, the description covers the high-level flow and cost but omits what the caller receives on success and how the payment/escrow parameters relate to the session. The rich input schema notes fill some gaps, but the tool description alone leaves notable operational context undefined.

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 some parameter-relevant context, such as the max-query session cap and the concrete listing slug, but it does not explain key parameters like open_tx_hash, proof_escrow_id, or the exactly-one-of slug/id rule. Schema description coverage is only 50%, so the tool description was expected to compensate further but does not fully do so.

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 states a specific action ('Buy per-query access to live data listings'), identifies the resource ('Open a prepaid session'), and even gives a concrete listing example with pricing. It clearly distinguishes itself from data_preview ('first taste free via data_preview'), making the tool's role unambiguous among siblings.

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 provides clear context for when to use this tool: when paid per-query access is desired, contrasting with free preview via data_preview. It also gives a sequential usage hint ('Open a prepaid session, then fund and query'), though it does not explicitly state when NOT to use the tool versus related session tools like data_session_fund or data_session_query.

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

All Hacker News Front Page (Live Tech Stories) — buy per-query in-session (hnfrontpage) toolsInspect
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