Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_query

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

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

Beyond the annotations, the description discloses real behavioral facts: cost of 0.01 USDC per query, a hard cap of 20 queries per session, and the required escrow funding path. These are exactly the economic and rate-limit details an agent needs before committing spend. It stops short of saying what happens to charges if the session is underfunded or what a successful call returns.

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 prerequisite sequence is compact and valuable, but the lead sentence 'Optional paid queries — competing is free' is a puzzling opener that should be replaced with the actual purpose. Embedding a single provider's marketing blurb ('AAAS Science Magazine research breakthroughs') in a generic query tool's description spends space on catalog detail rather than tool behavior.

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?

This is a paid, non-idempotent, non-read-only operation with five parameters and no output schema, so the description should explain what the query returns and how receipts/k work. Instead it covers only cost, cap, and the prerequisite chain, leaving the agent unable to predict the response shape or the meaning of key inputs.

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 coverage is only 40% across five parameters, so the description would need to compensate and it does not. It says nothing about 'k' (result count, 1-10) or 'delivery_receipt', and only obliquely touches the query content. Only the pricing context adds meaning beyond the schema, leaving the most ambiguous parameters undocumented.

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 opens with the vague and somewhat confusing phrase 'Optional paid queries — competing is free' rather than a clean verb+resource statement. The concrete meaning (run a prepaid query against a funded session at 0.01 USDC/query) only emerges from the pricing line and the prerequisite sequence. The schema title description 'Run a prepaid query against a funded data session' is clearer than the tool description itself.

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 chain 'data_session_open → data_session_funding_package (self-sign from buyer_address) → data_session_attach_escrow (open_tx_hash) → data_session_query' tells the agent precisely what must happen before this tool is callable, which is strong when-to-use guidance. However, it gives no when-not-to-use rule and does not distinguish this from data_session_queries (presumably a listing of past queries).

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