Skip to main content
Glama

Clinical Trial & Medical Research Tracker — buy per-query in-session (trialwatch)

data_session_query

Optional paid queries — competing is free. Listing: trialwatch: New Clinical Trials & Medical Research Results 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.3/5.0
Behavior4/5

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

Beyond the annotations, the description discloses pricing (0.01 USDC per query) and a hard session cap (max 20 queries/session), which are exactly the cost/limit facts an agent needs before invoking a paid operation. It does not explain what happens on insufficient escrow or whether a failed query consumes credit, leaving some behavioral gaps.

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?

It is short, but front-loading is poor: the 'competing is free' aside and the 'Listing: trialwatch:' fragment precede the actionable prerequisite sequence. The information is dense and useful but reads as ad copy glued to a workflow note rather than a structured definition.

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?

Pricing, rate limit, and the prerequisite chain cover the economics and ordering, but with 40% parameter coverage and no output schema, the description should say more about what a query returns and what `k` and the receipt parameters do. Adequate for gating the call, incomplete for invoking it correctly.

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%, so the description needs to compensate, but it never mentions `k`, `sandbox_receipt`, `delivery_receipt`, or the `query` string. Only `session_id` is indirectly referenced via the sequence, and even that is implied through `open_tx_hash` on a different tool. The three undocumented parameters remain opaque.

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 a listing/price line rather than a clear verb+resource statement. The actual action (run a prepaid query against a funded session) only appears in the schema's description field, so an agent must cross-reference to know what the tool does. The name and the sequence tail do imply querying a data session, but the phrasing is marketing-flavored rather than purpose-defining.

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 prerequisite chain (data_session_open → data_session_funding_package → data_session_attach_escrow → data_session_query) is explicit and tells the agent exactly what must precede a successful call. The 'competing is free' remark hints at an alternative path but never names a sibling tool or states when not to use this one.

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