medical-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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-drugsC | Search for drug information using FDA database |
| get-drug-detailsB | Get detailed information about a specific drug by NDC (National Drug Code) |
| get-health-statisticsB | Get health statistics and indicators from WHO Global Health Observatory |
| search-medical-literatureC | Search for medical research articles in PubMed |
| get-article-detailsC | Get detailed information about a specific medical article by PMID |
| search-drug-nomenclatureB | Search for drug information using RxNorm (standardized drug nomenclature) |
| search-google-scholarC | Search for academic research articles using Google Scholar |
| search-clinical-guidelinesB | Search for clinical guidelines and practice recommendations from medical organizations |
| check-drug-interactionsC | Check for potential drug-drug interactions between two medications |
| search-medical-databasesC | Search across multiple medical databases (PubMed, Google Scholar, Cochrane, ClinicalTrials.gov) for comprehensive results |
| search-medical-journalsC | Search specific medical journals (NEJM, JAMA, Lancet, BMJ, Nature Medicine) for high-quality research |
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 11 tools
Multiple tools have overlapping purposes that could cause confusion, such as search-medical-databases, search-medical-journals, search-medical-literature, and search-google-scholar all targeting article/research searches with unclear boundaries. Similarly, search-drug-nomenclature and search-drugs both handle drug searches but from different sources, potentially leading to misselection. The descriptions help somewhat, but the significant overlap reduces clarity.
The naming follows a consistent verb-noun pattern with hyphens (e.g., check-drug-interactions, get-article-details), which is predictable and readable. There are minor deviations, such as some tools using 'get' and others using 'search', but overall the convention is maintained throughout the set, making it easy to understand the tool functions at a glance.
With 11 tools, the count is reasonable and well-scoped for a medical information server, covering drug interactions, drug details, health statistics, clinical guidelines, and various search functionalities. It's slightly on the higher side but not excessive, as each tool appears to serve a distinct purpose within the medical domain, making it manageable for agents to navigate.
The tool set covers key areas like drug information, medical literature, and health statistics, but there are notable gaps. For example, it lacks update or delete operations for any resources, and there's no clear lifecycle management for medical data (e.g., no tools for patient records or treatment plans). While agents can work around this for information retrieval, the surface is incomplete for broader medical workflows.