Skip to main content
Glama
Sign In

1gateway

by io.github.code0xff
OverviewDiscussionsAdmin

Clinical trials search and readout catalysts (ClinicalTrials.gov): phase, status, enrollment, dates, sponsor

clinical_trials

Use when an agent researches drugs, diseases or biotech sponsors, or watches trial readouts. Input: condition, intervention (drug), sponsor or q (one or more), optional status, phase, limit, mode=catalysts with days (primary completion within N days, default 90). Output: JSON studies (NCT id, title, phases, status, enrollment, key dates, sponsor, conditions, interventions, countries, link). Example: ?condition=obesity&intervention=semaglutide&phase=3 Price: $0.01 USDC (Base or Solana) via x402.

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": "clinical_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search over study records
daysNocatalysts window in days (default 90)
modeNosearch (default, newest updates first) or catalysts (primary completion due soon, soonest first)
limitNoStudies to return (default 10)
phaseNoComma list: early1, 1, 2, 3, 4
statusNoComma list: recruiting, not_yet_recruiting, active, enrolling_by_invitation, completed, terminated, suspended, withdrawn
sponsorNoLead sponsor or collaborator
conditionNoDisease or condition
interventionNoDrug, device or other intervention (alias drug)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description must carry the burden, and it discloses the two things an agent most needs to know: the exact output shape (JSON studies with listed fields) and that calls cost $0.01 USDC via x402 on Base or Solana, which is a payment/auth precondition the agent must handle. It omits sorting behavior (partly covered by the mode param description), pagination, rate limits, and error/failure behavior.

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

Conciseness4/5

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

The description is telegraphic but ordered well: usage trigger, inputs, outputs, example, price. Every clause carries information, and the paid-access note is placed last where it is easy to find. The bullet-less "Input:/Output:/Example:/Price:" compression costs some readability but wastes no words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, zero-required, no-output-schema tool with no annotations, the description supplies the output field list, mode semantics, defaults, and the x402 payment requirement — enough to call it correctly. Remaining gaps are filter-combination semantics (AND vs OR across q/condition/sponsor) and result-set size/pagination, which are not stated anywhere.

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 description coverage is 100%, so the schema already documents every parameter, and the description mostly restates them (condition, intervention, sponsor, q, status, phase, limit, mode, days). Its only genuine addition is a worked combination example (?condition=obesity&intervention=semaglutide&phase=3) showing how filters compose, plus the default 90-day catalyst window. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb+resource pair via the title ("Clinical trials search and readout") and the body makes clear it returns ClinicalTrials.gov study records (NCT id, phases, status, enrollment, dates, sponsor). It also declares the two operating modes ("mode=catalysts" for readout watching vs default search), so an agent can distinguish the two behaviors of this one tool without opening the schema.

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?

"Use when an agent researches drugs, diseases or biotech sponsors, or watches trial readouts" gives explicit triggering contexts and maps the readout-watching case to mode=catalysts with a days window. No when-not guidance or named alternatives are given, though no sibling tool overlaps this domain, so the practical ambiguity is low.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 1gateway toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources