Skip to main content
Glama

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

data_preview

Read-onlyIdempotent

✅ No API key needed. Listing: trialwatch: New Clinical Trials & Medical Research Results. Price 0.01 USDC/query (max 20 queries/session). Sample questions: What clinical trials were posted today?; Show newly recruiting studies. FREE preview — no key, no payment. Try one of the sample questions now.

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_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoPublic listing slug. Defaults to the routed session's listing when connected via /mcp/data/{slug}/http.
questionNoOptional free-text question you'd ask this data (echoed back).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description does add genuinely useful context on top — no API key required and a 20 queries/session cap — but it never explains what the preview returns or why it is limited, and the header 'Price 0.01 USDC/query' sits awkwardly beside 'FREE preview — no key, no payment', leaving cost behavior muddled.

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 text opens with a checkmark and an API-key claim rather than the tool's action, then repeats itself ('No API key needed' / 'no key, no payment'), lists two sample questions and closes with a sales call to action. Promotional filler displaces the one sentence that matters — what the call actually returns.

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?

There is no output schema, so the description carries the burden of explaining return values, and it does not — 'public metadata only' appears solely in the schema description and the response shape is never described. For a preview endpoint whose entire value is the shape of what comes back, that is a material gap.

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 100%, so the baseline would be 3, but the description actively misleads on the 'question' parameter: it advertises sample questions to 'try now', while the schema states the question is merely 'echoed back'. An agent reading the description would expect an answer, not an echo, making this worse than saying nothing.

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 names the listing (trialwatch: New Clinical Trials & Medical Research Results) and labels the call a 'FREE preview', so the resource is identifiable, but it never states the actual verb/outcome — that it returns public listing metadata rather than answering the question. The only explicit statement of function lives in the input-schema description ('Free, guest-callable taste of a listing (public metadata only)'), not the tool description.

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?

No when-to-use guidance and no routing against siblings such as data_session_open or data_session_query, which are the obvious alternatives once a real query is wanted. 'Try one of the sample questions now' is a prompt-style call to action rather than a usage condition, and it never says what the preview gives you that a paid session does not.

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