Skip to main content
Glama

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

data_session_funding_package

Read-onlyIdempotent

Optional paid queries — competing is free. Listing: scinewsmag: Science News Magazine Articles (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/5.0
Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, so the description only needs to add context. It adds that the call returns fund instructions and surfaces a listing and per-query price, but it leaves unclear whether this tool itself incurs a charge and how the returned instructions should be used.

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 brief, but the opening fragment 'Optional paid queries — competing is free' and the abrupt 'Listing:' formatting make it less front-loaded than it could be. It avoids bloat, but the structure is not clean.

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 simple one-parameter read-only tool, the definition covers the session prerequisite and states at a high level what is returned. It still leaves gaps around how this funding package relates to the sibling funding/preflight tools and what the returned instructions contain, which matters more because there is no output schema.

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% for the single session_id parameter, and the schema itself says the UUID comes from data_session_open. The description repeats the timing hint but adds no format or selection semantics beyond the schema.

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 states that the tool returns fund instructions after opening a session, but it frames this around 'Optional paid queries' and a specific listing rather than clearly naming the resource (a funding package for a data session) or its role relative to other funding steps. An agent can infer it is a read that yields instructions, but the purpose is not sharply defined.

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 supplies a sequencing hint ('after data_session_open') and implies optionality for paid queries, but gives no explicit when-not conditions and does not name or distinguish alternatives such as the preflight or fund tools. Usage is implied rather than fully guided.

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