Skip to main content
Glama

CMS Open Payments general payments from drug and device

health_open_payments_cms
Read-only

CMS Open Payments (Sunshine Act) general payments from drug and device makers to US physicians, prescribers and teaching hospitals for a program year (2019-2025): company, recipient (name, type, NPI, specialty, city, state), amount (USD), date, form and nature of payment, related products, plus match count. Filter by company, recipient last name or NPI, state and product. 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_open_payments_cms"
  }
}

Input Schema

NameRequiredDescriptionDefault
npiNoRecipient's 10-digit NPI
pageNoPage number from 1 (default 1)
yearNoProgram year 2019 to 2025 (default 2025)
limitNoRecords to return, 1 to 100 (default 25)
stateNoRecipient's 2-letter state
companyNoPaying company name start, e.g. pfizer, medtronic
productNoDrug or device name start, e.g. eliquis
lastNameNoRecipient's last name, e.g. smith

Output Schema

NameRequiredDescriptionDefault
pageNo
yearNo
countNo
totalNo
sourceNo
paymentsNo
checkedAtNo

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?

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the pricing model ($0.002 per successful call via x402 USDC on Base/Solana, failed calls free), which is material context for whether and how to call it. It does not cover pagination limits or result-size behavior, but the cost/auth disclosure is the more valuable addition.

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 data-scope sentence comes first and is followed by a compact pricing sentence; nothing is wasted. The first sentence is long and dense with parenthetical field lists, but it remains readable and front-loaded.

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, annotations, and full parameter coverage already supplied, the description only needs to establish scope and cost, which it does. Minor gaps are pagination/total-count behavior and any note on how unfiltered queries behave.

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 all 8 parameters including examples and defaults. The description restates the filter set and the 2019-2025 year range without adding syntax, matching semantics (e.g., prefix vs exact match for company/product) beyond what the schema shows.

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 dataset (CMS Open Payments / Sunshine Act general payments), the payer and recipient populations, and the exact fields returned (company, recipient identifiers, amount, date, nature of payment, products, match count). An agent can immediately tell this apart from FDA-centric siblings like health_fda_recalls_enforcement or health_cms_medicare_part_d.

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?

It lists the available filter dimensions (company, last name, NPI, state, product) which implies how to narrow queries, but never states when this tool is the right choice versus alternatives or what happens if no filters are supplied. Usage is inferable rather than guided.

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