Skip to main content
Glama

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

data_session_query

Optional paid queries — competing is free. Listing: physorgwatch: Physics & Technology News 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

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and non-idempotent, so the mutating nature is known. The description adds real behavioral value: 0.01 USDC per query pricing and a hard cap of 20 queries per session. It does not disclose what happens when the quota or escrow is exhausted, whether failed queries are billed, or what a query 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?

A single long run-on sentence that front-loads a marketing line ("competing is free") and a vendor listing before any explanation of the operation. The sequence chain is compact and valuable, but the promotional listing content is padding relative to the tool's job.

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 payment-bearing, non-idempotent tool with no output schema and 40% parameter coverage, the description should explain billing on failure, quota exhaustion behavior, and the shape of a result or receipt. It covers cost and ordering but leaves the operational outcomes — the things an agent most needs before spending money — unstated.

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% across 5 parameters, and the description adds no meaning for any of them. The undocumented k, delivery_receipt, and (partially) sandbox_receipt parameters get no explanation, and "query" (max 4000 chars) is not clarified despite being the core input. The only parameter-like terms mentioned (buyer_address, open_tx_hash) belong to sibling tools.

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" and names it in the session sequence, so an agent can infer it runs a paid query. But it never states the specific verb+resource ("run a prepaid query against a funded session"), and the bulk of the text is a listing advertisement (physorgwatch pricing) rather than purpose. It does not distinguish this from the sibling data_session_queries or data_preview.

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 prerequisite chain (open → funding_package → attach_escrow → query) is genuinely useful context for when this tool becomes callable, and "competing is free" hints at a pay-vs-free choice. However, there is no explicit when-not-to-use guidance versus data_session_queries (historical lookups) or data_preview, and the prerequisite steps are stated as an ordering rather than as conditions.

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