Pharma MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENFDA_API_KEY | No | An openFDA API key is optional but raises the limits from 1,000 to 120,000 requests per day. Get one free at https://open.fda.gov/apis/authentication/. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_drug_labelsA | Search FDA drug labels (package inserts) by brand or generic name. Returns boxed warning, indications, contraindications, warnings and adverse reactions sections, trimmed, with a DailyMed link. |
| get_adverse_eventsB | Most frequently reported adverse reactions for a drug in FAERS (FDA Adverse Event Reporting System), with report counts. Optionally only serious reports. |
| signal_checkA | Pharmacovigilance signal check for a drug-reaction pair in FAERS: proportional reporting ratio (PRR) and reporting odds ratio (ROR) with 95% confidence intervals, Yates chi-squared, and whether it meets the Evans signal criteria. Use MedDRA preferred terms, e.g. 'PANCREATITIS'. |
| drug_recallsA | Recent FDA drug recalls (enforcement reports) matching a drug name, with classification (Class I is most serious), reason and status. |
| search_trialsB | Search ClinicalTrials.gov by condition, intervention and/or sponsor. Filter by status (e.g. RECRUITING, COMPLETED) and phase (PHASE1, PHASE2, PHASE3, PHASE4). Returns NCT id, title, phase, enrollment, dates, sponsor. |
| get_trialA | Full details of one clinical trial by NCT id: summary, eligibility criteria, primary outcomes, enrollment, sponsor and status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| drug_safety_brief | Draft a safety brief for a drug from its label, FAERS reports, recalls and ongoing trials. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct information need: drug label lookup, FAERS adverse event frequencies, pharmacovigilance signal statistics, recalls, trial search, and trial detail. The only near-overlap is search_trials vs get_trial and get_adverse_events vs signal_check, but the descriptions clearly separate search/detail and frequency/signal-analysis purposes.
All names use snake_case and most follow a verb_noun pattern, such as search_drug_labels, get_adverse_events, search_trials, and get_trial. Two names, signal_check and drug_recalls, deviate into noun-oriented phrasing, but the overall convention remains readable and predictable.
Six tools is well-scoped for a focused pharma safety and clinical trials server. Each tool covers a distinct resource or analysis operation, with no obvious filler tools.
The server covers drug labels, adverse events, signal detection, recalls, and clinical trial search/detail, which is strong lifecycle coverage for its apparent purpose. Minor gaps include drug-drug interactions and regulatory/approval lookup, but agents can work around these for most pharmacovigilance workflows.