Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_fund

Idempotent

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

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive, closed-world operation. The description adds genuinely useful context beyond that — that the platform executes the funding rather than the agent handling payment mechanics — but omits what happens to the funds (escrow, refundability, per-query vs. prepaid) and any failure modes, which matter for a payment action.

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?

It is short and front-loads the 'optional' framing, but the catalog-listing fragment is awkwardly embedded and the 'competing is free' clause is ambiguous enough to dilute the otherwise compact structure.

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?

For a financial mutation tool with no output schema, the description should clarify what gets charged, whether funds are escrowed or refundable, and how it relates to the release/refund siblings. It gestures at pricing (0.01 USDC/query) and platform-executed funding but leaves the money flow and post-funding lifecycle unexplained.

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?

With a single parameter and 100% schema description coverage, the schema already explains that session_id is the UUID from data_session_open. The description adds no further meaning about that parameter, 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 name says 'fund' but the description never states the verb directly; it circles the action with 'Platform-executes funding so you can data_session_query.' The middle sentence about 'Listing: scienceorgwatch: AAAS Science Magazine research breakthroughs (0.01 USDC/query)' reads more like catalog copy than a statement of what the tool does, leaving the core purpose inferable rather than explicit.

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?

'Optional paid queries — competing is free' implies this is only needed when paid listings are involved, and the closing clause implies it must precede data_session_query. However, it never names the obvious sibling alternatives such as data_session_funding_preflight or data_session_funding_package, and no explicit when-not condition is given.

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