get_landscape

Get Landscape

What it answers

Returns the CMS Landscape view of a Medicare plan: monthly consolidated premium, in-network MOOP, overall star rating, plan type, and the county/state service-area breadth. Filter by contract_id (required) + optional plan_id and year; omit plan_id to list all plans on a contract.

RETURNS a detail payload, not a plan-year count: value.plans is the actual PLAN LIST (report_year, plan_id, plan_name, org_name, plan_type, category, consolidated_premium, part_c_premium, part_d_premium, moop_in_network, overall_star_rating, service_area_county_count / state_count), sorted premium ascending so the cheapest plans lead; value.summary rolls it up (plan_count, premium min / median / max, zero-premium count, star min / max, total distinct counties); value.row_counts carries matched / returned / truncated and value.query the filters applied. `limit` bounds the plan list (default 200, max 2000); a truncated list always carries a caveat.

Covers ALL plan categories (MA, PDP, SNP, MMP, Cost), 2007-2026. The Landscape drops ~early September, ahead of the October benefits drop, so it is the first official view of the upcoming plan year. Pair with get_pbp_benefit (benefits) for the full picture. A contract / plan / year with no Landscape rows returns found=false with a not_found_reason.

SOURCE: CMS MA/Part-D Landscape source files.

Inputs

contract_id

string · required

limit

integer · optional

plan_id

string · optional

year

integer · optional

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 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 \
  -H "Authorization: Bearer $VLADA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contract_id":"<contract_id>"}'

curl https://api.vladahealth.com/v1/tools/get_landscape/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

tables: medicare_silver.fact_ma_landscape

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-19 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.