mymedi-ai-mcp-server

Physician industry payments (CMS Open Payments)

provider_payments

Read-only

Looks up CMS Open Payments Sunshine Act records by physician NPI, returning total pharmaceutical and device company payments, payment-type breakdowns, and top paying companies.

Instructions

Look up pharmaceutical and device company payments to a physician (Sunshine Act data). Returns total payments, breakdown by type, and top paying companies. Source: CMS Open Payments.

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": {
      "npi": "<npi>"
    },
    "name": "provider_payments"
  }
}

Input Schema

Name	Required	Description	Default
`npi`	Yes	10-digit NPI number of the physician

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.7.9Nov 2, 2026
- addedInput schema / properties / npi / maxLength
```
Added value: +500
```
Addedv1.2.1Apr 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly=true, destructive=false, openWorld=true, so the safety profile is covered. The description usefully discloses the return shape (totals, type breakdown, top companies) and the upstream source, but omits things that matter for CMS data: reporting-year coverage/lag, whether results are empty for physicians with no payments, and idempotency/mutability of upstream data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences plus a source tag, with the purpose and return contents front-loaded and zero filler. Every clause earns its place.

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 one parameter, full schema coverage, and no output schema, the description's summary of returned fields (totals, breakdown, top companies) fills the output-schema gap well. A note on data year/freshness and the no-payments case would make it complete.

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 coverage is 100% and the single npi parameter is fully documented as a 10-digit NPI, so the schema carries the load. The description adds nothing about the parameter (e.g., format validation, whether name lookup is possible), which is acceptable at this coverage level but not a value-add.

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?

"Look up pharmaceutical and device company payments to a physician" states a specific verb and resource, and the Sunshine Act/CMS attribution makes the data source unambiguous. It is clearly distinct from code/drug/claims siblings, though it does not explicitly separate itself from the closer provider_search/provider_enrich tools.

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?

Usage is implied by the required single parameter (a physician NPI), but the description never says when to prefer this over provider_enrich or how it relates to any other payment/compliance tool. No exclusions, prerequisites, or alternative routing are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.