Skip to main content
Glama

ACA Health Insurance Marketplace overview for a US ZIP code

health_health_insurance_exchange
Read-only

ACA Health Insurance Marketplace (HealthCare.gov) overview for a US ZIP code from CMS's QHP Landscape data: number of plans and insurers, plans per metal level, the cheapest plan of each metal level and the benchmark silver plan (second-lowest-cost silver, which sets ACA subsidies) with monthly premium before subsidies for the nearest published age, deductible and out-of-pocket maximum. Federal-platform states only. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "zip": "<zip>"
    },
    "name": "health_health_insurance_exchange"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoApplicant age 0-120 (default 40); premiums are published for 0-14, 18, 21, 27, 30, 40, 50 and 60
zipYes5-digit US ZIP code
yearNoPlan year: the newest CMS has published (default) or the year before, e.g. 2027 or 2026
countyNoOptional 5-digit county FIPS when the ZIP spans several counties

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / year / description
      Previous value: -"Plan year (only the year CMS publishes now)"New value: +"Plan year: the newest CMS has published (default) or the year before, e.g. 2027 or 2026"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover only read-only and open-world hints; the description adds meaningful behavior beyond them: the x402 payment mechanism ($0.002 per successful call, USDC on Base/Solana and 10+ networks), that failed calls are not charged, and the federal-platform coverage limitation. It also defines the non-obvious benchmark silver metric (second-lowest-cost silver, which sets subsidies) so the agent understands what a returned figure means.

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?

The definition is front-loaded with the data source and scope, then the returned fields, then the two constraints (state coverage, pricing). It is dense but nearly every clause carries information; the pricing/networks parenthetical is the only passage that runs longer than needed for tool selection.

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 an output schema present, return values need not be explained, and the description still enumerates the key metrics plus the benchmark definition. Remaining gaps, such as what happens when a ZIP has no federal-platform plans or how multi-county ZIPs are resolved, are partly handled by the optional county parameter.

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 100%, so all four parameters are already documented, establishing a baseline of 3. The description adds only one real semantic detail beyond the schema — premiums are reported for the 'nearest published age' — while the zip, year, and county parameters gain nothing further.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific dataset (CMS QHP Landscape), a specific resource (ACA Marketplace plans for a US ZIP code), and enumerates the exact outputs: plan/insurer counts, plans per metal level, cheapest per metal level, and the benchmark silver plan. An agent can tell immediately this is a ZIP-level ACA marketplace pricing lookup, not a general health-data query.

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?

It states a clear usage boundary — 'Federal-platform states only' — which tells the agent when not to call it, and the price/call model gives a cost-aware invocation rule. It does not name any alternative tool for state-based exchanges or for non-pricing plan browsing, but the sibling list contains no comparable marketplace tool, so the omission is minor.

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