get_landscape_benefit_change

Get Landscape Benefit Change

What it answers

What the plan design looked like for the SAME Medicare Advantage members in year Y and in year Y+1, member-weighted from the CMS Landscape files: total, Part C and Part D premiums and the $0 shares, the premium after full Extra Help, in-network MOOP and the share at or under $5,000, the Part D deductible and its $0 and standard shares, the tier-skips-deductible share, MA-PD and enhanced shares, the D-SNP $0 cost sharing, FIDE and HIDE shares, and the overall star. Y = every September-Y member's own plan; Y+1 = the same members' plan next year where it continues in their county (same_store, Day-One), or routed through the CMS crosswalk where that crosswalk is held (routed: continues + moved). The members whose plan departs and is not yet crosswalked are NOT in the Y+1 column, and the row says how many.

ARGUMENTS: transition_year (Y, default the newest held), group_by (national | product_type | parent | state | parent_by_product | state_by_product), product_type / state / parent (filters), metrics ('key' = the twelve headline metrics, 'all' = every metric, or a comma-separated list of metric names), weight (same_store | routed; routed is refused where the crosswalk is not held), include_cost_mmp (default false), limit (default 50, max 500, largest members first).

RETURNS value.rows (one per group: members_y, members_y1 and, per metric, {y, y1, change, unit}), value.summary (the national row for the same scope, the editions, the weight used) and value.metrics (the metric labels and units). Dollars are the filed monthly premium / annual MOOP or deductible in nominal dollars; pct metrics are shares of members in the metric's own domain (Part D metrics over MA-PD members, D-SNP metrics over D-SNP members).

RULES THE TOOL ENFORCES: member base H/R contracts, plans 001-799, matched to the Y file by plan and county; PDP never; industry excludes Cost and MMP unless asked; D-SNP is its own product type; a change is over the same members, never a mix of two populations. Suppressed cells count as zero, so every weight is a floor.

SOURCE: Vlada analysis of the CMS MA/Part D Landscape files, CMS monthly enrollment by plan and county, and the CMS plan crosswalk where held.

Inputs

group_by

string · optional

default: "national"

include_cost_mmp

boolean · optional

default: false

limit

integer · optional

metrics

string · optional

default: "key"

parent

string · optional

product_type

string · optional

state

string · optional

transition_year

integer · optional

weight

string · optional

default: "same_store"

Call it

From an agent: connect the Vlada MCP once (one click for Claude, ChatGPT, Cursor, VS Code) and ask in plain English; the agent selects get_landscape_benefit_change when the question fits. From code: the same tool over REST with an API key. The schema endpoint needs no key.

curl -X POST https://api.vladahealth.com/v1/tools/get_landscape_benefit_change \
  -H "Authorization: Bearer $VLADA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

curl https://api.vladahealth.com/v1/tools/get_landscape_benefit_change/schema      # the JSON schema, no auth
# MCP endpoint (Streamable HTTP): https://mcp.vladahealth.com/mcp

What comes back

Typed rows plus provenance on every answer: the public source file, its vintage, the methodology, and a response_hash you can replay. Prove and replay tools turn any number into a re-runnable receipt. A number the data cannot support comes back as “not in the data”, never as zero.

Sources behind it

medicare_silver.fact_ma_landscape
medicare_silver.enrollment_monthly_county
medicare_silver.plan_crosswalks_annual
medicare_semantic.fact_landscape_benefits_v1

tables: medicare_silver.fact_ma_landscape · medicare_silver.enrollment_monthly_county · medicare_silver.plan_crosswalks_annual

views: medicare_semantic.fact_landscape_benefits_v1

Known limits

No gaps recorded for this tool. Absence of a recorded gap is not a claim of complete coverage; the answer itself says what it covers.

As of the 2026-09-30 build of the served surface · machine-readable catalog · the live server may run a different version; the schema endpoint above is authoritative for what is deployed.