Skip to main content
Glama

Rxnorm

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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

TableJSON 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. 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."
  2. 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."
  3. 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."
  4. 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"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "rxcui": "7052"
+  }
+]
  6. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds valuable behavioral context beyond the annotations: it explains that NDCs attach to marketed products, that ingredient names are automatically expanded to products, and that the response explicitly indicates such expansion. It also discloses the historical NDC count behavior for non-marketed concepts, which prevents confusing empty responses. This goes well beyond the readOnly/idempotent hints.

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?

The description is three sentences, front-loaded with the main purpose, then provides essential behavioral details. Every sentence adds value: purpose, input flexibility, and edge-case behavior. No redundant or filler content.

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?

With a full input schema, output schema, and annotations (readOnly, openWorld, idempotent), the description covers all necessary context: input types, automatic expansion, and historical count behavior. It is complete for a single-parameter lookup tool, anticipating likely user confusions.

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 input schema describes the 'rxcui' parameter thoroughly, including that it can accept an RxCUI or drug name and how ingredient expansion works. Since schema_description_coverage is 100%, the description adds little new parameter-level meaning; it mostly reinforces what the schema already says. A baseline of 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 opens with 'Get the NDC (National Drug Code) identifiers for a drug', a specific verb+resource combination that clearly states the tool's function. It distinguishes itself from sibling tools like rxnorm_search and rxnorm_get_properties by focusing exclusively on NDC identifiers, making its purpose unmistakable.

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 provides clear context on when to use this tool (when NDC codes are needed) and what inputs are acceptable (RxCUI or plain drug name). However, it does not explicitly mention alternatives or exclusions, such as recommending rxnorm_search for general search or rxnorm_get_properties for other drug properties. The guidance is clear but not exhaustive.

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

All Rxnorm toolsInspect
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.

Resources