Dailymed

Search Drugs

search_drugs

Read-onlyIdempotent

Search Structured Product Labels by any combination of name, ANDA/NDA, NDC, RxCUI.

Input Schema

TableJSON Schema

Name	Required	Description
`ndc`	No	NDC code (11-digit)
`name`	No	Drug name (brand or generic)
`page`	No	1-based page (default 1)
`rxcui`	No	RxNorm RxCUI
`pagesize`	No	1-100 (default 25)
`manufacturer`	No	Manufacturer name
`application_number`	No	ANDA/NDA number (e.g. "NDA021436")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`metadata`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 23, 2026

addedOutput schema / properties / data

Added value: +{
+  "items": {
+    "properties": {
+      "published_date": {
+        "type": "string"
+      },
+      "setid": {
+        "type": "string"
+      },
+      "spl_version": {
+        "type": "number"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / metadata

Added value: +{
+  "properties": {
+    "current_page": {
+      "type": "number"
+    },
+    "current_url": {
+      "type": "string"
+    },
+    "db_published_date": {
+      "type": "string"
+    },
+    "elements_per_page": {
+      "type": "number"
+    },
+    "next_page": {
+      "type": [
+        "number",
+        "string"
+      ]
+    },
+    "next_page_url": {
+      "type": "string"
+    },
+    "previous_page": {
+      "type": "string"
+    },
+    "previous_page_url": {
+      "type": "string"
+    },
+    "total_elements": {
+      "type": "number"
+    },
+    "total_pages": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / pageNumber

Removed value: -{
-  "description": "Current page number",
-  "type": "number"
-}

removedOutput schema / properties / pageSize

Removed value: -{
-  "description": "Page size",
-  "type": "number"
-}

removedOutput schema / properties / results

Removed value: -{
-  "description": "Array of matching drug labels",
-  "items": {
-    "properties": {
-      "applicationNumber": {
-        "description": "NDA/ANDA number",
-        "type": "string"
-      },
-      "lastUpdate": {
-        "description": "ISO date of last update",
-        "type": "string"
-      },
-      "manufacturer": {
-        "description": "Manufacturer name",
-        "type": "string"
-      },
-      "name": {
-        "description": "Drug name",
-        "type": "string"
-      },
-      "ndc": {
-        "description": "NDC code",
-        "type": "string"
-      },
-      "rxcui": {
-        "description": "RxNorm RxCUI",
-        "type": "string"
-      },
-      "setId": {
-        "description": "DailyMed unique identifier for the label",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / totalPages

Removed value: -{
-  "description": "Total number of pages",
-  "type": "number"
-}

removedOutput schema / properties / totalResults

Removed value: -{
-  "description": "Total number of matching results",
-  "type": "number"
-}

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "Aspirin"
+  },
+  {
+    "manufacturer": "Bayer",
+    "ndc": "50090076501"
+  },
+  {
+    "application_number": "NDA021436"
+  },
+  {
+    "pagesize": 50,
+    "rxcui": "7677"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results for Structured Product Labels",
+  "properties": {
+    "pageNumber": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "pageSize": {
+      "description": "Page size",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of matching drug labels",
+      "items": {
+        "properties": {
+          "applicationNumber": {
+            "description": "NDA/ANDA number",
+            "type": "string"
+          },
+          "lastUpdate": {
+            "description": "ISO date of last update",
+            "type": "string"
+          },
+          "manufacturer": {
+            "description": "Manufacturer name",
+            "type": "string"
+          },
+          "name": {
+            "description": "Drug name",
+            "type": "string"
+          },
+          "ndc": {
+            "description": "NDC code",
+            "type": "string"
+          },
+          "rxcui": {
+            "description": "RxNorm RxCUI",
+            "type": "string"
+          },
+          "setId": {
+            "description": "DailyMed unique identifier for the label",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalPages": {
+      "description": "Total number of pages",
+      "type": "number"
+    },
+    "totalResults": {
+      "description": "Total number of matching results",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety and side-effect profile. The description adds that it searches across labels and supports combinations, which is consistent. It does not add details on rate limits or return behavior, but with annotations covering the main traits, this is adequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler. It front-loads the main action and resource, then lists the identifiers. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, 0 required, and an output schema present, the description covers the essential purpose and combination semantics. It doesn't mention pagination or defaults, but those are in the schema. The tool is simple enough that the description is sufficient for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all parameters are documented. The description adds the key insight that parameters can be used in any combination, which is not explicit in the schema. This goes beyond simply restating the schema, so it earns a point above the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Search') and resource ('Structured Product Labels'), and lists the searchable identifiers (name, ANDA/NDA, NDC, RxCUI). This clearly differentiates it from siblings like get_drug (single lookups) and list_labels_for_drug_name (specific listing).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies a general search use case and mentions combinable fields, but does not explicitly contrast with sibling tools or state when not to use it. It gives clear context for search operations without exclusions, so it's above minimal but not fully explicit about alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Dailymed tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.