Skip to main content
Glama

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

data_session_funding_package

Read-onlyIdempotent

Optional paid queries — competing is free. Listing: scinews: Latest science news & breakthrough headlines (0.01 USDC/query). Returns fund instructions after data_session_open.

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

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

B3.3/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive behavior, and the description adds useful context that this returns funding instructions rather than executing payment. It also lists a query product and price. It still does not explain whether calling itself incurs a cost, what the returned package contains, or how it relates to later funding steps.

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

Conciseness3/5

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

The definition is short, but the first sentence is confusing and partially non-sequitur, and the listing sentence is formatted awkwardly. It is not bloated, but some wording does not help an agent select or invoke 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?

For a one-parameter session tool with annotations but no output schema, the description gives the essential prerequisite and says it returns fund instructions. It remains thin on what the funding package actually provides, how multiple listings are handled, and what the agent should do with the returned instructions.

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%, and the single session_id parameter is fully documented in the schema as a UUID from data_session_open. The description reinforces the data_session_open prerequisite but does not add syntax or meaning beyond what the schema already provides.

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

Purpose4/5

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

The description states the tool returns fund instructions after data_session_open and gives a concrete listing example with a price. That is specific enough to understand the tool's role, though the opening phrase about optional paid queries and 'competing is free' is vague and does not cleanly distinguish it from funding-related siblings.

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

Usage Guidelines3/5

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

It implies the tool is used after data_session_open and is relevant for optional paid queries, which gives some usage context. However, it does not explicitly say when to use this instead of siblings such as data_session_funding_preflight or data_session_fund, so the agent must infer the routing.

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