Skip to main content
Glama

AAAS Science Magazine research breakthrough news (scienceorgwatch)

data_session_open

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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context the annotations lack: the session is prepaid, priced per query (0.01 USDC), and the listing caps at 20 queries per session. It omits what happens on open (what is returned, whether funds are reserved, what occurs if a session already exists), which matters for a non-idempotent create.

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 one sentence that matters ('Open a prepaid session, then fund and query') is clear and well-placed at the end, but it is preceded by promotional text and a nested-parenthesis listing blurb that do not help the agent invoke the tool. The most actionable instruction should be front-loaded rather than trailing the advertisement.

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 six-parameter, zero-required, non-idempotent session-creation tool with no output schema, the description covers the economic model and the downstream flow but leaves half the parameters unexplained and says nothing about what opening returns (a session id, a signing payload, a funding requirement). It is adequate to start a call but not sufficient to complete the flow confidently.

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 50%, and the uncovered parameters (max_queries, open_tx_hash, proof_escrow_id) receive no explanation in the description. The one useful addition is the listing-specific cap of 20 queries per session, which qualifies max_queries, but it sits in tension with the schema's declared maximum of 50 without reconciliation, and open_tx_hash and proof_escrow_id are never mentioned.

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 operative phrase 'Open a prepaid session, then fund and query' states a verb and resource, but it is buried behind marketing copy ('Optional paid queries — competing is free') and a specific listing advertisement. An agent can infer this initiates a paid data session, but the first half of the text describes a listing rather than the tool, which muddies the purpose.

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 sequencing clause 'then fund and query' implies this is the first step of a multi-step flow involving data_session_fund and data_session_query, which is implied usage rather than explicit routing. There is no statement of when not to use it, no prerequisites, and no guidance on choosing between this and data_session_funding_package or data_session_funding_preflight.

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