Skip to main content
Glama

CMS Medicare Part D prescriber rows: prescriber NPI, name

health_cms_medicare_part_d
Read-only

CMS Medicare Part D prescriber rows (by provider and drug): prescriber NPI, name, specialty, state, drug name, claims, 30-day fills and total drug cost. Filter by 10-digit NPI, or by generic drug name with an optional state. Up to 20 rows per call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "health_cms_medicare_part_d"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many rows, 1 to 20 (default 5)
npiNo10-digit prescriber NPI, optional (use this or generic)
stateNoTwo-letter state code, optional
genericNoGeneric drug name, letters and spaces, optional

Output Schema

NameRequiredDescriptionDefault
queryNo
sourceNo
checkedAtNo
prescriptionsNo

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 already declare readOnlyHint and openWorldHint, and the description adds useful behavior beyond them: a maximum of 20 rows per call, a $0.002 per-successful-call price, payment via x402 across multiple networks, and the fact that failed calls are not charged. It does not describe data vintage or latency, but the added cost and row-limit context is substantive.

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?

The description is compact and front-loads the dataset and fields before filters and pricing. It is slightly dense, but every clause carries useful information and there is no obvious filler.

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 an output schema, full parameter descriptions, and read-only/open-world annotations, the description provides enough context to call the tool correctly. The main remaining omission is data vintage, which would help an agent judge fitness for time-sensitive questions, but everything essential is present.

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 description coverage is 100%, so the schema already documents npi, generic, state, and max. The description reinforces the main filtering modes and the 20-row ceiling, but adds little semantic detail beyond what the schema provides, warranting the baseline 3.

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?

The description names a specific CMS dataset and lists the returned fields (prescriber NPI, name, specialty, state, drug, claims, fills, cost), making the tool's purpose clear. It does not explicitly distinguish itself from potentially overlapping siblings such as health_npi_provider_registry or health_physician_compare_cms, so it stops short of a 5.

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?

It tells the agent how to query the resource: by 10-digit NPI, or by generic drug name with an optional state. It does not state when to prefer this tool over alternatives or when not to use it, so it is clear but not fully prescriptive.

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