Skip to main content
Glama

ScienceNews Magazine Articles — buy per-query in-session (scinewsmag)

data_session_funding_preflight

Read-onlyIdempotent

Requires an agent API key (Authorization: Bearer or X-API-Key). Check whether the session's buyer wallet can fund its escrow before you broadcast. Returns {ready, missing[], actions[]}: missing names each gap (usdc, eth_gas, allowance) and actions holds the exact call that fixes it (a gas shortfall comes back as the faucet call). Reads chain balances only. REST twin: POST /api/v1/data-sessions/{session_id}/funding-package/preflight. Next: data_session_funding_package (self-sign) or data_session_fund.

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_funding_preflight"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still adds real value: the auth requirement (Bearer or X-API-Key), that it reads chain balances only (not internal ledger state), and the exact return shape. No rate limits or failure modes are described, but with annotations in place this is solid.

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?

Dense and mostly front-loaded, with the verification purpose stated immediately after the auth preamble. Every sentence carries information, though the auth line placed first and the REST twin path are arguably secondary for an agent deciding whether to call it.

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

Completeness5/5

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

There is no output schema, and the description compensates fully by enumerating the return shape ({ready, missing[], actions[]}) and the meaning of each gap value (usdc, eth_gas, allowance) plus the faucet action for gas shortfalls. Auth, purpose, sequencing and REST equivalent are all present, so nothing an agent needs is missing.

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?

One parameter at 100% schema coverage, so the schema already documents session_id as the UUID of a session you opened. The description mentions 'the session's buyer wallet' and that the owner comes from the key, which adds slight context but no syntax or format detail beyond the schema. Baseline 3 applies where the schema does the heavy lifting.

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 a specific verb and resource: check whether the session's buyer wallet can fund its escrow. The pre-broadcast timing frames it precisely, and it is clearly distinguishable from the funding siblings (package/fund) which are named as what comes after.

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?

Gives a clear trigger ('before you broadcast') and explicit next steps ('Next: data_session_funding_package (self-sign) or data_session_fund'), which routes the agent onward. It stops short of stating when this check can be skipped or when it is unnecessary, so it is not a full when/when-not/alternatives treatment.

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