Skip to main content
Glama

get_cms_open_payments_profile

Read-only

Use when assessing physician payment transparency risk, evaluating manufacturer relationships, or preparing Sunshine Act compliance reporting. Returns CMS Open Payments aggregates by physician or manufacturer — payment amounts, types, and program year breakdown. Example: Dr. Smith — $847K general payments from 3 manufacturers in 2022, 67% from one device company in consulting fees — concentration above $100K triggers enhanced compliance review. Source: CMS Open Payments Sunshine Act database. $0.02 USDC per call.

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": {
      "recipient_name": "<recipient_name>"
    },
    "name": "get_cms_open_payments_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
program_yearNo
recipient_nameYes
manufacturer_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious context: the upstream source (CMS Sunshine Act database), per-call cost ($0.02 USDC), and an interpretive threshold ($100K concentration triggering enhanced review) that shapes how results should be read. Return shape is described at a high level but not pagination or edge-case behavior.

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 usage trigger, then returns, then an example, then source and price — a sensible order with no filler sentences. The worked example is long and carries editorial interpretation ('concentration above $100K triggers enhanced compliance review') that is useful but slightly promotional in tone.

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 is the only source of return-value information, and it does supply the aggregate contents and a concrete result example. The main residual gap is filter interaction and result granularity (per-manufacturer rows vs totals) for a 3-parameter tool with zero schema documentation.

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 0%, so the description carries the burden. It does clarify the physician-vs-manufacturer dimension and that results break down by program year, and the example ('in 2022') hints that program_year is a calendar year number. However, it never states that recipient_name is the sole required parameter, nor how the two name filters combine when both are supplied.

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: returns CMS Open Payments aggregates by physician or manufacturer, with payment amounts, types, and program-year breakdown. This is clearly distinguishable from neighbors like get_cms_facility_benchmark or get_industry_spend_profile, which cover different CMS/intel datasets.

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 lead sentence gives three concrete use cases (payment transparency risk, manufacturer relationship evaluation, Sunshine Act compliance reporting), which is strong when-to-use guidance. It stops short of saying when to use a sibling instead or when this data would be inappropriate, so it lands at 4 rather than 5.

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