Skip to main content
Glama

ACA Premium Tax Credit Calculator

Federal poverty line for ACA premium tax credits

get_federal_poverty_level
Read-onlyIdempotent

Returns the federal poverty line (FPL) used for the ACA premium tax credit for a coverage year, household size and state, plus the 100%, 133%, 138%, 150%, 200%, 250%, 300% and 400% income thresholds. Coverage year Y uses the HHS guidelines published in year Y-1: 2026 coverage uses the 2025 guidelines ($15,650 for one person in the 48 states and DC, $19,550 Alaska, $17,990 Hawaii); 2025 coverage uses 2024; 2027 coverage uses 2026. Copied from the Federal Register notices, not model memory.

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": {
      "household_size": "<household_size>",
      "state": "<state>"
    },
    "name": "get_federal_poverty_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoCoverage (tax) year: 2025, 2026 or 2027. Default 2026.
stateYesState of residence: two-letter code or name (AK and HI have their own poverty lines; all other states and DC share one).
household_sizeYesTax family size: you, your spouse if filing jointly, and every dependent you claim.
household_incomeNoHousehold income in dollars for the coverage year: modified AGI of you, your spouse and dependents who must file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered. The description adds real context beyond that: provenance ('Copied from the Federal Register notices, not model memory') and the lag rule tying coverage year Y to year Y-1 guidelines, which is the kind of correctness detail an agent cannot get from annotations.

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?

Front-loaded with the resource and scope, then the year rule, then the provenance note. The parenthetical dollar figures are somewhat heavy but serve as a concrete sanity anchor; nothing is genuinely wasted.

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?

There is no output schema, and the description compensates by enumerating the returned thresholds (100% through 400%) and the FPL basis. The only real gap is the unexplained optional household_income input, which matters if the tool also derives an income percentage.

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%, so all four parameters are documented and the baseline is 3. The description does add the Y-1 guideline-year mapping, but it never mentions the optional household_income parameter or what it is for, leaving that input's role to the schema alone.

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?

States a specific verb and resource ('Returns the federal poverty line') plus the exact scope (coverage year, household size, state) and the derived thresholds returned. An agent can distinguish this pure lookup from the sibling calculation tools (calculate_premium_tax_credit, check_subsidy_cliff) without opening a schema.

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?

Gives clear operating context: the coverage-year-to-guideline-year rule and the AK/HI/rest-of-country split tell the agent how to frame a call. It never explicitly says when to use this versus the sibling tools that consume an FPL, so the routing is inferred rather than stated.

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.