Skip to main content
Glama

search_drug_ndc

Find drug product details by NDC, brand or generic name, labeler, dosage form, or route, and retrieve active ingredients and packaging information.

Instructions

Search the National Drug Code (NDC) Directory for drug product identification. Find drugs by NDC, brand name, generic name, labeler, dosage form, or route. Returns product details, active ingredients, and packaging information.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_drug_ndc"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of results to skip for pagination
limitNoMaximum results to return (1-100, default 10)
routeNoRoute of administration
brandNameNoDrug brand name
dosageFormNoDosage form (e.g., 'tablet', 'capsule', 'injection')
productNdcNoNational Drug Code (NDC)
genericNameNoDrug generic name
labelerNameNoDrug labeler/manufacturer name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the response shape ('product details, active ingredients, and packaging information') and implies a read-only lookup, but says nothing about filter combination logic, what happens with zero filters (all results?), or rate/limit behavior beyond what the schema states.

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?

Three short sentences, front-loaded with the resource name and immediately followed by the searchable fields and return content. No filler and no restatement of the name or title.

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?

For an eight-parameter, all-optional search tool with a fully described schema and no output schema, the description covers purpose, query dimensions, and return contents, which is nearly sufficient. The only meaningful miss is explaining how the optional filters interact and whether an unfiltered call is valid.

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?

Schema description coverage is 100%, so all eight parameters are already documented with meaning and, for skip/limit, bounds and defaults. The description only restates the searchable field set the schema already covers, adding no new semantics. Baseline 3 applies.

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

Purpose4/5

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

Names a specific verb and resource ('Search the National Drug Code (NDC) Directory for drug product identification') and enumerates the searchable dimensions: NDC, brand name, generic name, labeler, dosage form, route. This clearly separates it from a labels or adverse-events search, though it does not explicitly name which sibling to use for overlapping drug queries.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the enumerated lookup keys suggest when this tool fits (product/packaging identification), but there is no guidance on when to prefer another FDA tool, whether at least one filter is required, or whether multiple filters combine with AND semantics.

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