Skip to main content
Glama

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

data_session_fund

Idempotent

Optional paid queries — competing is free. Listing: techcrunchai: TechCrunch AI — industry news, funding & launches (0.01 USDC/query). Platform-executes funding so you can data_session_query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "data_session_fund"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds genuinely useful context beyond that: the platform executes the funding on the buyer's behalf and the price is 0.01 USDC per query. It omits what happens on insufficient balance, whether funds are escrowed/refundable, and the resulting session state.

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?

Short overall, but not front-loaded: the tool's actual behavior appears only at the end, and the marketplace listing text with a hardcoded price is noise that does not help an agent decide or invoke. Roughly half the text earns its place.

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?

This is a value-moving operation with no output schema, so the description must carry more weight: it should say what balance is drawn from, whether a fixed package or per-query amount is funded, and what state the session is left in. It supplies only a per-query price and a vague 'platform-executes funding', which is not enough for an agent to call a payment tool confidently.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself describing session_id as a UUID from data_session_open. The description adds no additional meaning about the identifier, so baseline 3 applies.

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 clause 'Platform-executes funding so you can data_session_query' is the only part that conveys the actual action, and it is buried after an unrelated opening line and an embedded listing blurb. An agent can eventually infer that this funds a data session to unlock paid queries, but the definition never states that plainly and never distinguishes itself from data_session_funding_preflight or data_session_attach_escrow.

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' is a weak, ambiguous framing that does not tell the agent when to fund versus when to run a preflight, attach an escrow, or just use free queries. The sequencing hint ('so you can data_session_query') is the only real usage guidance, and there are no exclusions or alternatives named.

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