Drug Labeling MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATABRICKS_HOST | Yes | Your Databricks workspace host URL. | |
| DATABRICKS_TOKEN | Yes | Your Databricks access token. | |
| DATABRICKS_MODEL_ENDPOINT | Yes | Your Databricks model-serving endpoint. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Starter MCP server for the GSA MCP hackathon. Replace this description, the tools, and the package name with your own service. See the repo README to get started.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_opioid_label_updatesB | Search FDA opioid label updates PDF. Returns relevant passages, similarity scores, and FDA PDF page references. |
| get_drug_labelD | – |
| get_drug_cyp_label_historyB | Retrieve available label revisions and passages mentioning target CYP enzymes. |
| get_latest_four_opioid_labelsB | Latest available openFDA record for four configured opioids, with LLM summary. |
| get_drug_cyp_label_detailsC | Retrieve CYP evidence for one FDA labeling record. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explore_dataset | Start an exploration session for a named dataset. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| server_info | Basic information about this MCP server. Replace with documentation specific to the API(s) you expose — a data dictionary, field reference, or usage notes the model can read directly. |
TDQS
Scored across 5 tools
Most tools target distinct operations, but get_drug_label has no description and may overlap with get_latest_four_opioid_labels and the CYP label tools. get_drug_cyp_label_history and get_drug_cyp_label_details also have a subtle boundary that may confuse an agent.
All tools use snake_case and begin with get_ or search_, which is mostly consistent. The name get_latest_four_opioid_labels embeds a specific count and differs slightly in style, but the overall convention is predictable.
Five tools is a well-scoped set for a focused drug-labeling server. Each tool appears to cover a distinct lookup or retrieval use case without excessive surface area.
The surface covers opioid label updates, latest opioid records, general drug label retrieval, and CYP evidence/history, but it lacks broader drug-label search or listing operations outside the opioid/CYP focus. The missing description on get_drug_label also leaves a notable usability gap.