Get one product record from an open drug data source
drugdata_get_productFetch one product record using a source and its own ID from openFDA, DSLD, DailyMed, or INKEEDecoder, returning source details, ingredients, links, and follow-up calls.
Instructions
Use this for an existing source+id, including an entity record or confirmed link; do not repeat a broad search. Fetch only needed records; selectively fetch supplied URLs with host web tools if more page content is needed. Fetch one product record from openFDA, DSLD, DailyMed, or INKEEDecoder. The id is the database's own key: a product NDC (openFDA), a numeric label id (DSLD), an SPL set id (DailyMed), or a product slug/URL (INKEEDecoder). The result carries the unified product ref, source-specific details, ingredient rows (roles, quantities, UNIIs when supplied by the source), links, and suggested follow-up calls. openFDA directory ingredient rows may lack identifiers. For SPL label UNIIs use drugdata_resolve_identifiers with include_label_ingredients: true. include_ingredients is true by default; false also skips DSLD ingredient mapping and enrichment. include_ingredient_enrichment adds DSLD nutrient CAS/group metadata with up to 20 extra serial requests, default false; it has no effect when ingredients are omitted. include_label_sections extracts DailyMed SPL usage sections — these are large and default false. page pages the ingredient and label-section collections one page at a time and re-fetches the record; it never walks pages automatically. A malformed id is an error result naming the search tool that finds a valid one; an upstream miss is an error result, not an empty product.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"source": "<source>",
"id": "<id>"
},
"name": "drugdata_get_product"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The database's own identifier: product NDC (openfda), numeric label id (dsld), SPL set id (dailymed), or slug/URL (inkeedecoder). | |
| page | No | Page number for ingredient and label-section collections, starting at 1. One page per call; the record is re-fetched and the tool never walks pages automatically. | |
| source | Yes | Upstream database that owns the record: 'openfda', 'dsld', 'dailymed', or 'inkeedecoder'. | |
| response_format | No | Text format: 'markdown' for a readable record, or 'json' for the structured result serialized as JSON. | markdown |
| include_ingredients | No | Include the product's ingredient rows with roles, quantities, and UNIIs when supplied by the source. openFDA directory rows may lack identifiers; use drugdata_resolve_identifiers with include_label_ingredients: true for SPL label UNIIs. Default true. | |
| include_label_sections | No | Extract DailyMed SPL usage sections (dosage, directions, patient guidance). Large — default false. Applies to dailymed products; false omits the sections and does not run the section parser. | |
| include_ingredient_enrichment | No | Add DSLD nutrient CAS/group metadata with up to 20 extra serial requests. Default false. Applies only to dsld when include_ingredients is true; ignored for other sources and when ingredients are omitted. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| links | Yes | ||
| details | Yes | ||
| product | Yes | ||
| summary | No | Source-faithful overview assembled from the record. | |
| nextSteps | Yes | ||
| pagination | Yes | ||
| ingredients | No | ||
| labelSections | No | ||
| labelIngredientsIncluded | Yes |