Skip to main content
Glama

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

data_session_open

Optional paid queries — competing is free. Listing: scinewsmag: Science News Magazine Articles (0.01 USDC/query (max 20 queries/session)). Open a prepaid session, then fund and query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_session_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
listing_idNoUUID of the listing. Provide exactly one of listing_slug or listing_id.
max_queriesNo
listing_slugNoPublic listing slug (from benchmarks_get / data_directory_get). Provide exactly one of listing_slug or listing_id.
open_tx_hashNo
buyer_addressNoBuyer EVM address. Optional: defaults to your own platform wallet when omitted.
proof_escrow_idNo

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 readOnlyHint=false, non-idempotent, non-destructive, closed-world behavior. The description adds prepaid pricing and a per-session max of 20 queries, but does not explain what session state is created, whether opening itself charges, or failure/retry behavior.

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 very short and its action sentence is clear, but it starts with a context line ('Optional paid queries — competing is free') and a fragmentary 'Listing:' line that introduce ambiguity. There is little waste, but the structure is not optimally front-loaded.

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 mutation that opens a session with six optional parameters and no output schema, the description omits what is returned, such as a session identifier, and how that result feeds data_session_fund or data_session_query. Annotations cover safety flags but not the return/next-step contract, leaving the definition under-complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%, and the description mentions listing context plus a 20-query session cap that loosely relates to max_queries. It does not explain listing_slug vs listing_id, open_tx_hash, proof_escrow_id, or reinforce the buyer_address default, so it does not compensate for the uncovered parameters.

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 phrase 'Open a prepaid session' gives a specific verb and resource, and 'then fund and query' positions it before data_session_fund/query. It is not fully sharp because the opening line 'Optional paid queries — competing is free' does not describe the tool itself, and the listing line is a fragment.

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?

The description indirectly says to use this before funding and querying ('then fund and query'), and the free-vs-paid note implies paid queries are optional. It does not explicitly name when not to use it, prerequisites, or alternatives beyond the basic sequence.

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