Skip to main content
Glama

Stratalize Intelligence

Get Nadac Drug Benchmark

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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-schema behavior: weekly CMS refresh cadence, HTTP 503 with no charge on upstream failure, a per-call x402 price, and restatement_detected for republished effective dates. The one weak spot is the closing provenance sentence, which gestures at an output_hash binding without explaining what an agent should do with it.

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 use condition, then results, then example, then source and SLA — a sensible order with little redundancy. The trailing provenance/hash clause is dense boilerplate that most callers cannot act on and slightly dilutes the otherwise tight paragraph.

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 one-parameter, no-output-schema tool, the description does the heavy lifting: it enumerates the returned fields, gives an example value, discloses the data source and refresh cadence, and covers the failure mode. The residual gap is input-side, namely how name lookups resolve, rather than any missing output or behavioral context.

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?

There is a single parameter, ndc_or_name, with 0% schema description coverage, so the description carries the full burden. It shows a valid 11-digit NDC example and mentions normalized ndc11, which conveys the NDC form, but it says nothing about name matching (brand vs generic, partial strings, ambiguity or no-match behavior). Adequate but incomplete for the one input that matters.

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: retrieve CMS NADAC drug acquisition cost benchmarks, keyed by NDC or name. A concrete worked example (NDC 42385096230 — $1.45422/EA) removes any ambiguity about the unit of the returned figure, and the scope (per-unit acquisition cost, not contract or reimbursement rates) distinguishes it from the GPO contract and other pricing siblings.

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 names the personas and the decision context (contract negotiation, payer comparison), which is a clear when-to-use signal. It does not explicitly state when not to use it or name an alternative for adjacent needs, but the use case is narrow and unambiguous enough that an agent can route correctly.

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