Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_funding_package

Read-onlyIdempotent

Optional paid queries — competing is free. Listing: scienceorgwatch: AAAS Science Magazine research breakthroughs (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

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that fund instructions are returned after data_session_open, but it does not explain what the funding package contains, whether invoking it incurs cost, or how it relates to the funding workflow.

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 description is short, but it is fragmented and front-loads an unclear marketing phrase ('Optional paid queries — competing is free') before the actionable information. The listing and pricing details are specific but not clearly tied to the tool's invocation behavior.

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 single-parameter, read-only tool with full schema coverage and annotations, the description is minimally adequate. However, without an output schema, it should more clearly explain what 'fund instructions' means and how this package fits between data_session_open, funding preflight, and funding itself.

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 description coverage is 100%, and the single session_id parameter is fully documented in the schema as the UUID from data_session_open. The description adds no parameter meaning beyond the schema, which is acceptable but does not compensate further.

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 description hints that the tool returns fund instructions after data_session_open and references a specific listing with a price, but it never clearly states that it produces a funding package for an existing data session. It is distinguishable as funding-related, but not clearly differentiated from siblings such as data_session_funding_preflight or data_session_fund.

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?

The only usage guidance is the precondition 'after data_session_open'. There is no explicit guidance on when to use this instead of data_session_funding_preflight, data_session_fund, or other funding-related siblings, and no when-not-to-use conditions.

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