Skip to main content
Glama

Stratalize Intelligence

Get Cms Open Payments Profile

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds genuinely useful behavior beyond them: the upstream source (CMS Open Payments Sunshine Act database), explicit per-call pricing of $0.02 USDC, and the shape of the returned aggregates. The $100K concentration threshold is analytical guidance rather than tool behavior, and it does not cover empty-result handling for unmatched names.

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 case, then return shape, then an illustration, source, and price — a logical order with no filler sentences. The worked example is longer than strictly necessary and its invented specifics ($847K, 67% from one device company) could be mistaken for real output rather than illustration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only lookup with no output schema, the description does substitute for the missing return documentation by listing payment amounts, types, and program-year breakdown, plus source and cost. However, the 0% parameter coverage and the absence of any no-match/empty-result behavior leave real gaps for an agent composing a call with an ambiguous recipient_name.

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 whole burden. It implies recipient_name is a physician, manufacturer_name is a company, and program_year is a year filter (the example uses 2022), but never states accepted name formats, whether name matching is exact or fuzzy, or whether manufacturer_name filters rather than groups. Partial but not adequate compensation.

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 concrete verb and resource — 'Returns CMS Open Payments aggregates by physician or manufacturer — payment amounts, types, and program year breakdown' — so the agent knows exactly what data comes back. It does not name or contrast itself against any sibling (e.g. get_industry_spend_profile), so it stops short of full disambiguation.

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?

Three explicit triggering conditions are given: physician payment transparency risk, manufacturer relationship evaluation, and Sunshine Act compliance reporting. That is clear context for selection, but no 'do not use when' or named alternative is offered for adjacent spend/benchmark tools.

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