Skip to main content
Glama

Science News Tracker — latest research & discovery headlines (scinews)

data_session_fund

Idempotent

Optional paid queries — competing is free. Listing: scinews: Latest science news & breakthrough headlines (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.4/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 partly covered. The description does add one genuinely useful behavioral fact — that the platform executes the funding transfer rather than the agent — but it says nothing about cost source, balance requirements, or what happens on insufficient funds, which matter for a payment mutation.

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 not front-loaded: the actual behavior ('Platform-executes funding') appears last, after a slogan and a marketplace listing that reads like ad copy rather than tool documentation. Sentence fragments and mixed registers make it harder to parse than a single clear statement would be.

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 payment/mutation tool with no output schema, so the description must carry the burden of explaining what funding does and what it returns. It omits whether funding is per-query or per-package, where the funds come from, and the result of a successful call — all essential for correct invocation.

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 100% with a single well-documented session_id, so the schema carries parameter meaning fully. The description adds nothing beyond it — no note that the session must be open or unfunded, nor any format detail. Baseline 3 applies.

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

Purpose2/5

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

The name implies funding a data session, and the fragment 'Platform-executes funding so you can data_session_query' gestures at that, but the opening sentence ('Optional paid queries — competing is free') and the embedded listing ad ('scinews: Latest science news & breakthrough headlines (0.01 USDC/query)') obscure what the tool actually does. An agent cannot tell from this text whether the tool funds a session, purchases a listing, or runs a query.

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' and the trailing 'so you can data_session_query' weakly imply this precedes querying, but there is no explicit when-to-use or when-not guidance. Nothing distinguishes it from the closely named siblings data_session_funding_package, data_session_funding_preflight, or data_session_attach_escrow, which is a serious routing gap given how many similar names exist.

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