Look up the vetted analytic VIEWS for a question before you query. A view is the decision that comes before any table or chart: who is counted (population), against what base, compared to what, over which period and vintage, and what one row is (grain); plus the weight, the named measures, the forms that draw it (draw_as), how to reach the data (reach: the typed tool that carries the population and base first, then the source codes to read with describe_data_source and query_substrate), the rules that must hold and the ways the view goes wrong or contradicts another view (contradicts_if). Pass the user's question in their words; add a domain (ma_market, ma_benefits, hospital_prices, payer_rates, medicare_benchmark, ma_stars, medicaid, marketplace, drug_pricing, formulary, pbm, providers, employer, mlr, hospital_quality, drug_policy, ma_value, cross_domain) or a level (executive for a headline, actuarial for weights, cohorts, decompositions and distributions, detailed for row-level lookups) when you know it. Returns up to 8 views, best first; the default is 4. Use the returned population, base and period in your call and say them in the answer. A view is analytical guidance: it grants no data access and proves no coverage for the places, dates or populations in your question. Verify coverage with the source's own card before you quote a number. A question no view covers is composed from the same fields.