@ythalorossy/openfda 1.1.0 → 1.3.0

package/README.md

@@ -8,16 +8,26 @@ A Model Context Protocol (MCP) server for querying drug information from the Ope
 
 ## Features
 
-- Retrieve drug label information by brand name
+- Retrieve drug label information by brand name, with `limit` (default 1, max 25) and `skip` to page through the rest of the matching labels — the first match is not necessarily the most canonical one, and `substance_name` leads each record so a combination product is obvious at a glance
 - Retrieve drug information by generic (active ingredient) name
 - Get all brand versions of a generic drug
-- Get adverse event (side effect) reports for a drug (by brand or generic name)
+- Get adverse event (side effect) reports for a drug (by brand or generic name), with paging via `skip` (maximum 25000) and ordering via `sort` (`receivedate:desc` / `receivedate:asc`) — without `sort`, results are a deterministic earliest-`report_id` slice, so a small sample is not representative
+- Rank adverse-event values for a drug by frequency (e.g. the most commonly reported reactions) via `get-drug-adverse-event-counts`; returns `{term, term_code, count}` — for coded fields (`serious`, `patient.patientsex`, `patient.reaction.reactionoutcome`) `term` is a decoded human-readable label and `term_code` carries the raw upstream value, while text fields pass through unchanged in both; note that openFDA omits a result total on aggregated responses, so this tool reports no total
 - Retrieve all drugs manufactured by a specific company
-- Get comprehensive drug safety information (warnings, contraindications, interactions, precautions, etc.)
-- Retrieve full Drugs@FDA application data for a given section and field
+- Get comprehensive drug safety information (warnings, contraindications, interactions, precautions, etc.); `generic_name` is `null`, not `"Unknown"`, when the label carries no structured generic or substance name
+- Retrieve Drugs@FDA application data for a given section and field, with a `limit` parameter and a real `Showing N of M` total; can also search by `sponsor_name`, which is stored uppercase and normalised automatically. `detail` controls the record shape and defaults to `summary` (application number, sponsor, products and a `submission_count`, with no `submissions` array); `detail: 'full'` adds the `submissions` array, capped at 10 per record, plus `submissions_truncated` when more were omitted. This default changed in 1.3.0 — code written against an earlier version that read `results[].submissions` directly must now pass `detail: 'full'`
 - Normalize and validate NDC (National Drug Code) formats
 - Helpful error messages and suggestions for failed queries
 
+> **Route vocabularies differ across tools.** `openfda.route` (used by
+> `get-drug-by-name`, `get-drug-by-generic-name`, `get-drug-by-ndc`,
+> `get-drug-by-product-ndc` and `get-drugs-by-manufacturer` — the SPL route
+> of administration) and `products[].route` (used by `get-drugsfda` — the
+> Drugs@FDA product route) are different controlled vocabularies. The same
+> insulin glargine product is reported as `SUBCUTANEOUS` in one and
+> `INJECTION` in the other, so joining or filtering on route across tools
+> will silently miss matches.
+
 1. **Set up your OpenFDA API Key**
 
    The server reads `OPENFDA_API_KEY` from its process environment. It is
@@ -59,7 +69,8 @@ A Model Context Protocol (MCP) server for querying drug information from the Ope
                   "get-drug-safety-info",
                   "get-drug-by-ndc",
                   "get-drug-by-product-ndc",
-                  "get-drugsfda"
+                  "get-drugsfda",
+                  "get-drug-adverse-event-counts"
               ]
           }
       }