drug-label
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port for the HTTP server when running in hosted mode. Defaults to 3000. | 3000 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_drugA | Resolves a brand or generic name, misspelling or NDC through RxNorm: ingredients, brands, FDA classes, and the best manufacturer labels (not repackagers) with set ids. Never guesses between look-alike names. |
| label_sectionA | Returns one topic of the official FDA label as the label's own text under its headings, citing the label's set id, version and date. Says so when the label has no such section. |
| recalls_shortagesA | FDA drug recalls (class, reason, status, date, product) and shortage records (status, company, reason) for a drug, newest first, from openFDA. |
| search_labelB | Finds every paragraph of the official FDA label that mentions a term (another drug, grapefruit, alcohol, a condition), with its section heading and topic. |
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 4 tools
Each tool targets a distinct concern: drug name/NDC resolution (find_drug), retrieving a specific label section (label_section), obtaining recalls/shortages (recalls_shortages), and full-text label searching (search_label). There is no overlap or ambiguity about which tool to use for a given task.
All names use lowercase snake_case and are descriptive, but they mix verb-first (find_drug, search_label) and noun-first (label_section, recalls_shortages) patterns. This is a minor deviation from a strictly consistent verb_noun convention, but the naming remains predictable and readable.
With only 4 tools, the server is tightly scoped to the core needs of FDA drug label information: identification, label access, searching, and safety alerts. This is well within the 3–15 tool range and each tool earns its place without redundancy.
The tool surface covers the essential lifecycle: find a drug, retrieve a section, search across the label, and check recalls/shortages. A minor gap is the lack of a way to list all available sections or retrieve the full label at once, but the existing tools combined can achieve most user needs without failure.