DailyMed MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_dailymed_contextB | Get comprehensive information about DailyMed database, its purpose, content types, and when to use it |
| get_drug_detailsC | Get detailed information about a specific drug by its SET ID |
| get_drug_historyC | Get version history for a specific drug by its SET ID |
| get_drug_ndcsC | Get NDC codes for a specific drug by its SET ID |
| get_drug_packagingC | Get packaging information for a specific drug by its SET ID |
| get_drug_mediaC | Get media links (images, documents) for a specific drug by its SET ID |
| get_all_drug_namesB | Get all available drug names in the DailyMed database with pagination support |
| get_all_drug_classesB | Get all available drug classes in the DailyMed database with pagination support |
| get_all_ndcsA | Get all available NDC codes in the DailyMed database with pagination support |
| get_all_rxcuisA | Get all available RxCUI codes in the DailyMed database with pagination support |
| get_all_uniisC | Get all available UNII codes in the DailyMed database with pagination support |
| get_all_application_numbersB | Get all available FDA application numbers in the DailyMed database with pagination support |
| get_download_linksC | Get download links for ZIP and PDF files of a specific drug by its SET ID |
| search_splsA | Search for Structured Product Labels (SPLs) using either simple drug name search or advanced DailyMed API parameters. When using simple query, searches for drugs first then finds related SPLs. When using advanced parameters, queries DailyMed SPLs API directly. Supports pagination for large result sets. |
| search_rxcuisC | Search for RxCUI codes using various parameters with pagination support |
| search_drug_namesB | Search for drug names using various parameters with pagination support |
| search_uniisC | Search for UNII codes using various parameters with pagination support |
| search_application_numbersB | Search for FDA application numbers (NDA, ANDA, etc.) using various parameters with pagination support |
| search_drug_classesB | Search for pharmacologic drug classes using various parameters with pagination support |
| get_mapping_statisticsB | Get statistics about loaded mapping files |
| search_by_rxnorm_mappingC | Search for RxNorm mappings by drug name |
| get_rxnorm_mappings_for_setidC | Get RxNorm mappings for a specific SET ID |
| get_pharmacologic_class_mappings_for_setidC | Get pharmacologic class mappings for a specific SET ID |
| get_mappings_by_rxcuiC | Get mappings for a specific RxCUI |
| get_rxnorm_mappings_by_pharmacologic_classC | Find RxNorm mappings for drugs that belong to a specific pharmacologic class SET ID |
| get_all_pharmacologic_class_setidsB | Get all pharmacologic class SET IDs that have associated drug mappings |
| get_pharmacologic_class_detailsC | Get detailed information about a pharmacologic class including FDA context and classification attributes (uses mapping file data) |
| search_drugs_by_pharmacologic_classB | Search for drugs using DailyMed drug class codes (from the drug classes API). Supports pagination for large result sets. |
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 28 tools
Most tools have distinct purposes targeting specific resources like drugs, classes, or codes, with clear boundaries. However, some overlap exists between 'get_all_' and 'search_' tools (e.g., get_all_drug_names vs. search_drug_names), which could cause minor confusion in selection, though descriptions help clarify the pagination differences.
Tool names follow a highly consistent verb_noun pattern throughout, using 'get_' for retrieval and 'search_' for queries, with snake_case uniformly applied. This predictability makes it easy for agents to understand and navigate the toolset without ambiguity.
With 28 tools, the count is borderline high for a medical database server, potentially feeling heavy and overwhelming. While the domain is complex, the number might exceed typical well-scoped ranges (3-15 tools), suggesting some consolidation could improve usability without losing functionality.
The toolset provides comprehensive coverage for the DailyMed domain, including CRUD-like operations for drugs, classes, and codes (e.g., get details, search, mappings), with no obvious gaps. It supports core workflows like retrieval, search, and mapping across all key resources, ensuring agents can handle most tasks without dead ends.