Skip to main content
Glama

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

data_session_fund

Idempotent

Optional paid queries — competing is free. Listing: trialwatch: New Clinical Trials & Medical Research Results (0.01 USDC/query). Platform-executes funding so you can 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>"
    },
    "name": "data_session_fund"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesUUID of a data session you opened (from data_session_open).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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, idempotent funding operation. The description adds useful context that funding is platform-executed and references a price of 0.01 USDC/query, but it does not explain payment flow, sandbox behavior, or what happens to funds if queries are not made.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but poorly structured as disconnected fragments. "Optional paid queries — competing is free" adds ambiguity rather than useful context, and the main action is not front-loaded.

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 funding mutation involving payment, the description does not explain the session state required, the cost implications, or how this sandbox funding differs from real funding. It leaves too much inferred for an agent to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single session_id parameter is fully documented in the input schema. The description adds no parameter-specific meaning beyond the schema, so the baseline 3 is appropriate.

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 hints that the tool performs funding so that data_session_query can be used, but it never plainly says it funds a data session. The phrase "Optional paid queries — competing is free" is vague and does not help distinguish it from funding-related siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the tool is used before data_session_query, but gives no explicit conditions for when to use it versus data_session_funding_package, data_session_funding_preflight, or data_session_attach_escrow. There are no when-not or prerequisite guidelines.

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