Medical Research MCP Suite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache time-to-live in milliseconds for performance tuning | 3600000 |
| FDA_API_KEY | No | Optional API key for FDA database | |
| PUBMED_API_KEY | No | Optional API key for PubMed with higher rate limits | |
| MAX_CONCURRENT_REQUESTS | No | Maximum number of concurrent API requests | 10 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ct_search_trialsC | Search ClinicalTrials.gov for studies with AI-enhanced results |
| ct_get_studyC | Get detailed study information by NCT ID with AI analysis |
| pm_search_papersC | Search PubMed for research papers with enhanced analysis |
| fda_search_drugsC | Search FDA drug database with safety analysis |
| fda_adverse_eventsC | Get adverse event reports for a drug with analysis |
| research_comprehensive_analysisC | Comprehensive analysis combining clinical trials, literature, and safety data |
| research_drug_safety_profileC | Complete drug safety analysis across clinical trials and FDA reports |
| research_competitive_landscapeC | Analyze competitive landscape across all databases |
| research_executive_summaryC | Generate executive summary for drug/condition analysis (context-friendly) |
| research_clinical_detailsC | Detailed clinical trials analysis for specific drug/condition |
| research_literature_detailsC | Detailed literature analysis for specific drug/condition |
| research_safety_detailsC | Detailed safety and FDA analysis for specific drug |
| research_market_detailsC | Detailed market and competitive analysis for specific drug/condition |
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 13 tools
Tools have overlapping purposes, especially among the 'research_' prefixed ones (e.g., research_clinical_details, research_safety_details, research_drug_safety_profile, research_comprehensive_analysis), which could cause confusion about which to use for specific analyses. However, descriptions provide some differentiation, such as focusing on clinical trials, safety, or combined data.
Most tools follow a consistent pattern with prefixes like 'ct_', 'fda_', 'pm_', and 'research_' followed by descriptive names, though there are minor deviations (e.g., 'ct_get_study' vs. 'ct_search_trials' uses different verbs, and 'research_executive_summary' is more abstract). Overall, naming is readable and mostly predictable.
With 13 tools, the count is well-scoped for a medical research suite, covering multiple databases (ClinicalTrials.gov, FDA, PubMed) and various analysis types (search, details, safety, summaries). Each tool appears to serve a distinct purpose within the domain, justifying its inclusion.
The tool set provides comprehensive coverage for medical research, including search and detailed analysis across clinical trials, literature, safety data, and market insights. It supports full workflows from data retrieval (e.g., ct_search_trials) to integrated analyses (e.g., research_comprehensive_analysis), with no obvious gaps for the stated purpose.