Skip to main content
Glama

Clinical Trials Search - ClinicalTrials.gov studies

clinical_trials
Read-onlyIdempotent

Search ClinicalTrials.gov (official v2 API) by keyword, condition, intervention, sponsor or location. Returns NCT id, title, status, phases, enrollment, conditions, interventions, sponsor, dates and countries. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/clinical-trials.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "RECRUITING",
      "maxItems": 10,
      "condition": "obesity",
      "intervention": "semaglutide"
    },
    "name": "clinical_trials"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFree-text search
statusNoOverall status
sponsorNoSponsor, e.g. Pfizer
locationNoLocation, e.g. Germany
maxItemsNoMax results (1-50)
conditionNoCondition, e.g. diabetes
interventionNoDrug or intervention, e.g. semaglutide

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the description is not obligated to restate safety. It does add genuinely useful operational context the annotations cannot carry: the upstream source (ClinicalTrials.gov v2), a hard rate limit of 25 calls/day per IP, and the paid x402 fallback at $0.005/call. It stops short of explaining what happens when the free quota is exhausted or how results are paged/ordered.

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

Conciseness5/5

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

Three sentences, front-loaded with what the tool does, then the return payload, then cost/limits. The return-field enumeration is compact and earns its place because no output schema exists.

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 7-parameter, all-optional search tool with no output schema, the description covers source, return shape, cost and rate limits adequately. Remaining gaps are pagination/result-window behavior and what an empty-filter call returns, which an agent might need to call it correctly at scale.

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% and every parameter already carries an example, so the schema does the heavy lifting. The description's enumeration of search dimensions largely restates those parameters without adding matching semantics (e.g. AND vs OR across filters, whether query is combined with condition).

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

Purpose4/5

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

The description gives a specific verb and resource ('Search ClinicalTrials.gov (official v2 API)') plus the five search axes (keyword, condition, intervention, sponsor, location) and the fields returned. The purpose is unambiguous, but it never contrasts itself with the closest sibling, literature_search, which an agent could reasonably consider for research-style queries.

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

Usage Guidelines3/5

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

Usage is only implied by the domain: an agent can infer 'use this to find clinical trials.' There is no statement of when to prefer it, when not to use it, or which combination of filters is required versus optional (all 7 parameters are optional, which is never addressed).

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