Skip to main content
Glama

Drug acquisition cost (CMS NADAC)

rx_price
Read-only

Latest CMS NADAC (National Average Drug Acquisition Cost) per-unit prices for a drug name, brand name or NDC, from data.medicaid.gov (monthly pharmacy invoice survey, weekly files). Groups by NADAC description, pricing unit (EA, ML, GM), generic or brand rate class and OTC flag, each with min, median and max unit cost across NDCs, effective date, NDC count, sample NDCs, and a 30-unit acquisition cost for per-dose EA items. Single-source generics map to RxNorm brand names. Price: $0.01 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": {
      "q": "<q>"
    },
    "name": "rx_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesDrug name, brand name or NDC, optionally with strength (e.g. metformin, Lipitor 20 mg, 00003-0894-21)
strengthNoStrength filter text matched against NADAC descriptions, e.g. 20 MG, 500 MG/5 ML, 100 UNIT/ML

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / strength / examples
      Removed value: -[
      -  "20 MG"
      -]
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavioral context: monthly pharmacy invoice survey with weekly files, grouping by NADAC description/pricing unit/rate class/OTC flag, aggregation across NDCs with min/median/max, and a 30-unit acquisition cost for per-dose EA items. Most valuably, it discloses the billing model — $0.01 per successful call in USDC via x402 v2, with failed and zero-match calls uncharged — which is critical for an agent deciding whether to call.

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 core purpose, then progressively discloses grouping dimensions, aggregation, and billing. The long enumeration of returned fields is dense but earns its place as a substitute for a missing output schema; only minor trimming would be possible.

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 no output schema, the description fully carries the return-value burden: grouping keys, aggregate statistics, effective date, NDC count, sample NDCs, and the 30-unit acquisition cost. Combined with source, refresh cadence, and cost model, an agent has everything needed to decide and call correctly.

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%, so both q and strength are already documented in the schema. The description confirms that q accepts a drug name, brand name or NDC and that strength can be folded into the query, but adds no matching/formatting rules or examples beyond what the schema supplies. Baseline 3 is appropriate.

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: 'Latest CMS NADAC per-unit prices' for a drug name, brand name or NDC, with the upstream source named. It is clearly distinct from rx_drug/rx_ndc in substance, but it never explicitly says which sibling to prefer when an agent merely wants NDC metadata, so it stops short of full sibling differentiation.

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 by the resource ('prices for a drug name, brand name or NDC'), and the note that single-source generics map to RxNorm brand names hints at input flexibility. However, there is no explicit when-to-use or when-not-to-use guidance and no named alternative among the rx_* siblings, leaving routing to inference.

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