Skip to main content
Glama

Medical & Health News Breakthroughs — buy per-query in-session (medicalxpresswatch)

data_session_query

Optional paid queries — competing is free. Listing: medicalxpresswatch: Medical & Health News 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.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description adds genuinely useful behavior the annotations can't express: cost of 0.01 USDC per query and a cap of 20 queries per session. It does not explain what happens on failure or whether a failed query is still billed, which matters for a non-idempotent paid call.

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 useful, but the sentence is cluttered with a listing/promo fragment ("Listing: medicalxpresswatch: Medical & Health News Breakthroughs...") that is marketing copy rather than invocation guidance. The key action verb is buried behind the pricing preamble.

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 paid, non-idempotent mutation with no output schema, the description supplies the two most decision-relevant facts (price and quota) plus the funding prerequisites. However, it leaves the receipt parameters and the shape of a successful/failed response entirely unexplained, so an agent still lacks enough to call it confidently in edge cases.

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 40%, so the description must compensate, but it says nothing about k, query, delivery_receipt, or sandbox_receipt. The identifiers it does mention (buyer_address, open_tx_hash) belong to other tools' inputs, not to this tool's five parameters.

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 leads with "Optional paid queries — competing is free" and gives pricing and a prerequisite sequence, but never plainly states that this tool executes a query against an already-funded session. The actual operation is only inferable from the name and the trailing step in the sequence, so it's vague rather than specific about the action.

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?

It explicitly encodes the prerequisite chain: data_session_open → data_session_funding_package (self-sign from buyer_address) → data_session_attach_escrow (open_tx_hash) → data_session_query, and warns that competing (free) is an alternative. It doesn't contrast with sibling listing tools like data_session_queries, but the ordered prerequisite flow is strong, actionable guidance.

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