Dailymed

Recent Updates

recent_updates

Read-onlyIdempotent

Return the most recently updated FDA Structured Product Labels from DailyMed (NLM), up to 100 results, ordered by update date descending. Useful for tracking newly revised drug labeling.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	1-100 (default 25)

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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"
+    },
+    "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 / pageSize

Removed value: -{
-  "description": "Number of results returned",
-  "type": "number"
-}

removedOutput schema / properties / results

Removed value: -{
-  "description": "Recently updated 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"
-      },
-      "setId": {
-        "description": "DailyMed unique identifier",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / totalResults

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

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "limit": 10
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Recently updated Structured Product Labels",
+  "properties": {
+    "pageSize": {
+      "description": "Number of results returned",
+      "type": "number"
+    },
+    "results": {
+      "description": "Recently updated 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"
+          },
+          "setId": {
+            "description": "DailyMed unique identifier",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "totalResults": {
+      "description": "Total available results",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint) already cover safety and idempotence, lowering the bar. The description adds behavioral context beyond annotations by specifying the source (DailyMed/NLM), the maximum result count (100), and the ordering (update date descending). This is useful and non-redundant.

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?

Two sentences, zero waste. The first sentence states the core functionality with all key constraints, and the second gives a clear use case. It is perfectly front-loaded and every phrase contributes value.

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

Completeness5/5

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

For a simple read-only tool with one optional parameter, an output schema present, and annotations already covering safety, the description is complete. It specifies what is returned, from where, the ordering, the limit, and a practical use case. Nothing essential is missing.

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

Parameters3/5

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

The schema description covers 100% of the parameter 'limit' with '1-100 (default 25)', so the schema does the heavy lifting. The description adds only the phrase 'up to 100 results', which reinforces the maximum but offers no new meaning. Baseline 3 is appropriate.

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 ('Return'), a precise resource ('FDA Structured Product Labels from DailyMed (NLM)'), and adds constraints (up to 100 results, ordered by update date descending). This clearly distinguishes it from sibling tools like label_history or search_drugs, which focus on different operations. The use case 'tracking newly revised drug labeling' further clarifies intent.

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 gives a clear context: 'Useful for tracking newly revised drug labeling.' This implies when to use it (when you need to see recent label updates). However, it does not explicitly name alternatives or state when not to use it, so it falls short of a perfect 5 but is still strong.

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.