clinicaltrials-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_trialsA | Search ClinicalTrials.gov for trials matching a condition. Returns a ranked list with status, phase, sponsor, site count, and a brief summary. WITHDRAWN and TERMINATED trials are excluded by default — pass status= to override. Results are ordered with RECRUITING trials first. |
| get_trial_detailsA | Get a full structured summary of one clinical trial by NCT ID. Returns: overview, what's being studied, verbatim eligibility criteria, site locations, and whether results have been posted. NCT ID hyperlink appears at the top and bottom for easy verification. |
| compare_trialsA | Compare 2 to 5 clinical trials side by side. Produces structured tables for design, timeline, locations, endpoints, and eligibility criteria. Use compare_on to focus on one category. |
| get_trial_resultsA | Fetch posted results for a clinical trial: participant flow, baseline characteristics, primary and secondary outcomes, and adverse events. Handles 4 cases: results posted, trial ongoing, completed but no results posted, and NCT ID not found. Adverse events default to serious events (Grade 3+) only. |
| find_recruiting_nearA | Find actively recruiting trials for a condition near a location. Results are grouped by location ring: trials in the queried city first, then elsewhere in the country. Location is city/country level — CT.gov has no GPS radius data. IMPORTANT: filtered by overall trial status, not individual site status. A site in your city may still show 'Not yet recruiting' even if the trial is recruiting globally. Always verify the specific site status at clinicaltrials.gov. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: searching, getting details, getting results, comparing, and finding recruiting trials by location. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., search_trials, get_trial_details) using underscores, making them predictable and easy to understand.
5 tools cover the essential operations for clinical trials access without being excessive or insufficient, making the server well-scoped.
The set covers searching, details, results, comparison, and location-based filtering. Minor gaps like advanced filters or site-specific status do not hinder primary workflows.