Skip to main content
Glama

Rxnorm Ndc

rxnorm_ndc
Read-onlyIdempotent

Get the NDC (National Drug Code) identifiers for a drug, the 11-digit US pharmacy codes used for billing, dispensing and inventory. Takes an RxCUI or a plain drug name ("amoxicillin", "Lipitor"). NDCs attach to marketed products rather than to an ingredient, so an ingredient or brand name is expanded to its products automatically and the response says it did so; a concept with nothing currently marketed reports its historical NDC count instead of an unexplained empty list.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
rxcuiYesRxNorm concept ID, or a drug name, resolved to an RxCUI automatically. A bare ingredient ("amoxicillin") works: it is expanded to its marketed products. A full dose phrase ("lisinopril 10 mg oral tablet") returns that one product's complete list.

Output Schema

NameRequiredDescriptionDefault
ndcsYesNational Drug Code identifiers
rxcuiYesRxNorm concept unique identifier
ndc_countYesNumber of NDC codes found

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID, or a drug name — resolved to an RxCUI automatically. A bare ingredient (\"amoxicillin\") works: it is expanded to its marketed products. A full dose phrase (\"lisinopril 10 mg oral tablet\") returns that one product's complete list."New value: +"RxNorm concept ID, or a drug name, resolved to an RxCUI automatically. A bare ingredient (\"amoxicillin\") works: it is expanded to its marketed products. A full dose phrase (\"lisinopril 10 mg oral tablet\") returns that one product's complete list."
  2. Changed1 schema field changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID, or a drug name — resolved to an RxCUI automatically. Prefer the full dose phrase (\"lisinopril 10 mg oral tablet\") over a bare ingredient (\"lisinopril\"): NDCs attach to specific products, so the ingredient-level concept returns an empty list."New value: +"RxNorm concept ID, or a drug name — resolved to an RxCUI automatically. A bare ingredient (\"amoxicillin\") works: it is expanded to its marketed products. A full dose phrase (\"lisinopril 10 mg oral tablet\") returns that one product's complete list."
  3. Changed1 schema field changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID, or a drug name (e.g. \"aspirin\") — resolved to an RxCUI automatically."New value: +"RxNorm concept ID, or a drug name — resolved to an RxCUI automatically. Prefer the full dose phrase (\"lisinopril 10 mg oral tablet\") over a bare ingredient (\"lisinopril\"): NDCs attach to specific products, so the ingredient-level concept returns an empty list."
  4. Changed1 schema field changed
    • changedInput schema / properties / rxcui / description
      Previous value: -"RxNorm concept ID"New value: +"RxNorm concept ID, or a drug name (e.g. \"aspirin\") — resolved to an RxCUI automatically."
  5. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "ndc_count": {
      +      "description": "Number of NDC codes found",
      +      "type": "integer"
      +    },
      +    "ndcs": {
      +      "description": "National Drug Code identifiers",
      +      "items": {
      +        "description": "NDC code in standard format",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "rxcui": {
      +      "description": "RxNorm concept unique identifier",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "rxcui",
      +    "ndc_count",
      +    "ndcs"
      +  ],
      +  "type": "object"
      +}
  6. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "rxcui": "7052"
      +  }
      +]
  7. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new behavior: automatic expansion of ingredient/brand names to marketed products, disclosure that the response reports the expansion, and that an unmarketed concept returns a historical NDC count rather than an unexplained empty list. That is meaningful context beyond the annotations, though nothing is said about result size or performance.

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

Conciseness4/5

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

Three sentences, front-loaded with the resource definition and followed by input forms and edge-case behavior. Dense but each sentence carries distinct information; the parenthetical definitions are slightly verbose but justified for an acronym-heavy domain.

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 a single-parameter, read-only lookup with a fully documented schema and an output schema, the description covers the inputs and the two surprising outcomes (auto-expansion, historical-count fallback). An agent could invoke it correctly from this text; only the absence of guidance on when to choose a sibling leaves a residual gap.

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 coverage is 100% and the single rxcui parameter is already described in detail, including the dose-phrase case ('lisinopril 10 mg oral tablet'). The description restates the same dual-input behavior plus the ingredient-expansion note rather than adding syntax or format detail the schema lacks, so the baseline of 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?

States a specific verb and resource — 'Get the NDC (National Drug Code) identifiers for a drug' — and explains what NDCs are ('11-digit US pharmacy codes used for billing, dispensing and inventory'). It clearly distinguishes the returned artifact (NDC codes) from the concept-level lookups implied by siblings like rxnorm_get_properties, though it never names an alternative tool.

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?

Gives concrete when-to-use context by specifying accepted inputs ('an RxCUI or a plain drug name') with examples, and warns that NDCs attach to marketed products, so an ingredient name is expanded automatically. It does not state when to prefer a sibling such as rxnorm_get_properties or rxnorm_search instead, so it stops short of explicit alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.