Skip to main content
Glama

NDC product lookup with price and recalls

rx_ndc
Read-only

Full product record for one package NDC: normalized NDC forms; RxNav status, RxCUI, concept name and history; labeler, marketing category, status and dates, application number, DEA schedule, imprint, color, shape and size from RxNav; brand and generic name, dosage form, route, active ingredients with strengths and package description from the openFDA NDC Directory; latest CMS NADAC unit cost; openFDA recall enforcement reports from the last 36 months. Price: $0.02 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

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": {
      "ndc": "<ndc>"
    },
    "name": "rx_ndc"
  }
}

Input Schema

NameRequiredDescriptionDefault
ndcYesPackage NDC, 10-digit dashed, 11-digit dashed or undashed, or undashed 10-digit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover read-only and open-world character, so the description's job is to add the rest — and it does: it discloses the pricing model ($0.02 per successful call, USDC via x402 v2), that failed and no-match calls are free, and that recall coverage is bounded to the last 36 months. That billing and data-freshness detail is exactly the kind of trait annotations cannot express. It stops short of noting rate limits, latency, or partial-failure behavior when one upstream source is unavailable.

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?

Front-loaded with the purpose, followed by the field inventory and a separate pricing sentence — a logical order with no filler. The long semicolon-delimited field enumeration is dense, but since there is no output schema it earns its place as the only description of return values.

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?

With one fully documented parameter and no output schema, the definition supplies the missing return-value picture, data provenance, recall window, and cost model. It is nearly complete; the remaining gap is failure/degradation semantics when an upstream source (RxNav, openFDA, CMS) is down or a record is only partially populated.

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 schema already enumerates all accepted NDC formats, so the baseline applies. The description only reinforces that it must be a single package-level NDC, which is a small but real clarification (package vs. product NDC) beyond the schema text.

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?

Opens with a specific verb+resource+scope: 'Full product record for one package NDC,' then enumerates the exact data domains returned (RxNav identity, openFDA NDC Directory attributes, CMS NADAC price, recall enforcement reports). This composite-aggregate framing is clearly distinguishable from the narrower siblings rx_ndc_convert, rx_price and rx_recalls without needing their schemas.

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?

The word 'Full' implies this is the everything-at-once lookup versus the specialized siblings, and 'one package NDC' implies singular-item use. But there is no explicit when-to-use/when-not statement and no sibling is named as an alternative for callers who only want price or only want recalls. Usage is inferable rather than stated.

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.

Resources