Skip to main content
Glama

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

data_session_query

Optional paid queries — competing is free. Listing: scinews: Latest science news & breakthrough headlines at 0.01 USDC per query (max 20 queries/session). Sequence: data_session_open → data_session_funding_package (self-sign from buyer_address) → data_session_attach_escrow (open_tx_hash) → 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>",
      "query": "<query>"
    },
    "name": "data_session_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
session_idYesUUID of a data session you opened (from data_session_open).
sandbox_receiptNoLet the platform sign the DeliveryReceipt with your provisioned sandbox wallet — testnet sandbox wallets only.
delivery_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses concrete economics the agent cannot get from structured fields: 0.01 USDC per query and a hard cap of 20 queries per session. That quota and cost disclosure is exactly the kind of behavioral context annotations don't carry, though it omits what happens when the cap is hit or when the session is underfunded.

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?

It is a single dense block that front-loads a confusing slogan ("competing is free") before getting to pricing and the workflow. The ordering and chain notation work, but the opening clause and the embedded listing pitch do not earn their place in a tool definition.

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 mutating, payment-consuming tool with no output schema and 40% parameter coverage, the prerequisite sequence and pricing partially fill the gap. Key gaps remain: undisclosed k and delivery_receipt semantics, and no statement of what a successful query returns or whether it is billed on failure or retries.

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 only 40% (session_id and sandbox_receipt are documented; query, k, and delivery_receipt are not), so the description needs to compensate and does not. It never explains what k does, what delivery_receipt is for, or what the query string should contain, leaving three of five parameters semantically opaque.

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 frames the tool as "Optional paid queries" with a per-query price and a named listing (scinews), which hints at running a paid query, but the opening clause "competing is free" is marketing noise that muddies the actual purpose. It never states plainly that it executes a query against a funded session, and offers no differentiation from siblings like data_session_queries.

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

Usage Guidelines4/5

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

The explicit workflow chain (data_session_open → data_session_funding_package → data_session_attach_escrow → data_session_query) is genuinely useful sequencing that tells the agent what must precede this call, including the self-sign hint from buyer_address and the open_tx_hash argument. It stops short of saying when NOT to use this tool or naming alternatives for the same job.

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