Skip to main content
Glama

get_nadac_drug_benchmark

Read-only

Use when a pharmacy buyer, 340B program manager, or CFO agent needs CMS NADAC drug acquisition cost benchmarks for contract negotiation or payer comparison. Returns latest NADAC per unit, effective_date, as_of_date, pricing_unit, ndc_description, normalized ndc11, source ndc, and restatement_detected when CMS republishes the same effective date. Example: NDC 42385096230 — NADAC $1.45422/EA as_of 2026-07-15 effective 2026-06-17. Source: CMS NADAC (data.medicaid.gov DKAN, weekly). | x402 SLA: $0.02 USDC per call. Returns HTTP 503 (no charge) when upstream data sources unavailable. data_sources[] discloses provenance string bound by synthesis.output_hash.

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_or_name": "<ndc_or_name>"
    },
    "name": "get_nadac_drug_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
ndc_or_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantially more: weekly CMS refresh cadence, restatement_detected semantics when CMS republishes an effective date, a metered cost of $0.02 USDC per call, and no-charge HTTP 503 behavior on upstream failure. It also discloses provenance via data_sources[] bound to an output hash, which is exactly the kind of behavior annotations cannot convey.

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 trigger condition, then returns, example, source, and SLA terms in a compact pipe-delimited block. Every element is substantive, though the dense separators and inline SLA/pricing boilerplate make it slightly harder to scan than a clean sentence structure would.

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 no output schema, the description correctly enumerates return fields (nadac per unit, effective_date, as_of_date, pricing_unit, ndc_description, ndc11, source ndc, restatement_detected) plus cost and error behavior. The main omission is any clarification of name-based lookup, which matters for a required parameter whose name promises two input modes.

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 0% for the single required parameter, so the description must carry the burden. It supplies a concrete NDC example (42385096230) implying the expected format, but never explains the 'or_name' half of ndc_or_name — whether a drug name is accepted, and how ambiguous names are resolved.

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?

States a specific verb and resource — CMS NADAC drug acquisition cost benchmarks — with an explicit audience (pharmacy buyer, 340B program manager, CFO). The naming and framing clearly separate it from siblings like get_drug_adverse_events, get_drug_recall_status, and get_gpo_contract_benchmark.

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 opening clause gives a concrete when-to-use condition (contract negotiation, payer comparison) tied to named roles. It does not explicitly exclude or route to the nearest alternative such as the GPO contract benchmark, so it stops short of full alternative guidance.

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