Skip to main content
Glama

TechCrunch AI News — buy per-query in-session (techcrunchai)

data_session_open

Optional paid queries — competing is free. Listing: techcrunchai: TechCrunch AI — industry news, funding & launches (0.01 USDC/query (max 20 queries/session)). Open a prepaid session, then fund and query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_session_open"
  }
}

Input 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. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare the non-readonly, non-destructive, non-idempotent profile, so the bar is lower. The description usefully adds pricing (0.01 USDC/query, max 20 queries/session) and the prepaid-session model with a required funding step, which is real context not in the annotations. It still omits whether opening itself charges, what is created (session id vs on-chain tx), and failure/expiry 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 text is mis-front-loaded: an obscure 'optional paid queries' fragment and an inline example listing with doubly nested parentheses occupy the opening, while the actual instruction is the last clause. Several tokens (the entire 'Listing: techcrunchai...' block) are example payload rather than guidance an agent needs to select and call the tool.

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, so the description must carry the lifecycle, and it does sketch open → fund → query plus pricing. But for a paid, non-idempotent session-creation tool it omits the return shape, whether a transaction hash argument (open_tx_hash) is needed up front, and how subsequent funding siblings tie in, leaving gaps an agent must discover by trial.

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 coverage is 50%, and the schema's own docstring already explains listing_slug/listing_id exclusivity and the buyer_address default. The description adds only the per-session query cap, which loosely maps to max_queries, and never mentions open_tx_hash or proof_escrow_id. That is a fair baseline-3 contribution, no more.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The operative verb+resource, "Open a prepaid session," appears only at the very end and is preceded by a fragment about optional paid queries and a hard-coded 'techcrunchai' listing example. An agent can extract that this opens a paid data session, but it must filter out demo data to get there. No sibling names appear, so differentiation from data_session_attach_escrow or data_session_funding_package is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Optional paid queries — competing is free" hints that this is a paid path versus a free alternative, and "open, then fund and query" implies sequencing. However, it never states prerequisites (e.g. USDC balance, which sibling to call before or after), and it gives no explicit condition for choosing this tool over the many adjacent data_session_* tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources