Skip to main content
Glama

Medicare Part D drug coverage from CMS monthly formulary

health_formulary_coverage_lookup
Read-only

Medicare Part D drug coverage from CMS monthly formulary files, current and next plan year: for a drug (name or RxCUI), in one plan, across a state's plans or over every formulary: coverage per strength, cost-share tier, prior authorization, step therapy, quantity limit, IRA negotiated-price flag, 30-day retail/mail cost, plan premium and deductible. Includes the CMS release date. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls 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": {
      "drug": "<drug>"
    },
    "name": "health_formulary_coverage_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugYesDrug name (generic or brand, e.g. atorvastatin, Eliquis) or an RxCUI
planNoOptional plan id CONTRACT-PLAN[-SEGMENT], e.g. H0028-007 or S4802-075
yearNoPlan (contract) year, e.g. 2026 or 2027. Default: the current year if loaded, else the newest
limitNoMax plans in a state listing, 1-100 (default 20)
stateNoOptional 2-letter state: list the plans sold there with this drug's coverage

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the data vintage ('CMS monthly formulary files, current and next plan year', 'Includes the CMS release date') and a full billing model: $0.003 per successful call, paid via x402 in USDC across multiple chains, with failed calls not charged. Cost and payment requirements are exactly the kind of operational context 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?

The purpose and data source are front-loaded, then the query scopes, then the returned fields, then pricing — a sensible order. The middle clause is a long enumeration, but each item is a distinct output field that helps the agent decide whether to call it; nothing is obviously padding.

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 an output schema present, the description need not explain return structure, and it still covers source, temporal scope, query modes and cost. Combined with annotations declaring a safe read operation, an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning by framing 'plan', 'state' and the unfiltered case as distinct result shapes rather than just optional filters. It does not add format or validation detail (e.g. RxCUI normalization, ambiguity handling) beyond the schema, so it sits just above baseline.

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?

The description names a specific verb and resource ('Medicare Part D drug coverage from CMS monthly formulary files') and enumerates exactly what is returned per drug: coverage per strength, tier, prior authorization, step therapy, quantity limit, IRA negotiated-price flag, 30-day cost, premium and deductible. An agent can distinguish this from generic CMS or drug-information siblings without opening the schema.

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 lays out the three query modes clearly — one plan, a state's plans, or every formulary — which maps directly onto when to pass 'plan' versus 'state' versus neither. What is missing is explicit routing against sibling tools or a stated 'when not to use this' condition, 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