Skip to main content
Glama

Physics & Technology News — buy per-query in-session (physorgwatch)

data_session_open

Optional paid queries — competing is free. Listing: physorgwatch: Physics & Technology News (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.8/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation, so the safety profile is covered. The description adds real context that sessions are prepaid and cost 0.01 USDC per query with a per-session query cap, but it omits what opening actually creates or returns (session token/id) and whether the open call itself charges anything. The stated 'max 20 queries/session' also sits in tension with the schema's max_queries maximum of 50.

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?

Three short sentences, so length is fine, but the ordering is wrong: the front-loaded text is a marketing aside and a specific example listing rather than the tool's action. The single genuinely useful instruction ('Open a prepaid session, then fund and query') appears last.

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?

A six-parameter session-creation tool with no output schema needs the description to explain what a successful open yields and how the identifier is used downstream. Instead the description is dominated by one example listing's pricing and gives no return-value or follow-up detail, leaving the agent under-informed for a paid, non-idempotent lifecycle step.

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 description adds no parameter meaning at all: listing_slug vs listing_id exclusivity, max_queries, open_tx_hash, buyer_address defaulting, and proof_escrow_id are all left entirely to the schema. Worse, the lead sentence implies a fixed listing and a 20-query cap, which conflicts with the schema's documented maximum of 50 and the ability to target any listing.

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 clause 'Open a prepaid session, then fund and query' does state a specific verb and resource, but it is buried behind a hardcoded example listing ('physorgwatch: Physics & Technology News...') and a pricing slogan ('Optional paid queries — competing is free'). The description never contrasts the tool against nearby siblings such as data_session_get (existing session) or data_session_fund, so the agent must infer the boundary itself.

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?

'Open a prepaid session, then fund and query' does communicate sequencing among the session lifecycle tools, which is genuine guidance. However, it never states when not to open a session (e.g. reuse an existing one via data_session_get) nor when data_session_attach_escrow or data_session_funding_preflight is the right call instead, so selection is only implied.

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