Skip to main content
Glama

Car Loan Interest Deduction Calculator

2025 and 2026 federal brackets and standard deduction

get_tax_brackets_and_standard_deduction
Read-onlyIdempotent

Returns the official 2025 and 2026 federal income tax brackets and standard deductions after the One Big Beautiful Bill Act: 2026 standard deduction $16,100 single, $32,200 joint, $24,150 head of household (Rev. Proc. 2025-32), 2025 $15,750 / $31,500 / $23,625, plus the additional amount for age 65 or blind. Optionally computes the tax and marginal rate on a taxable income. Says plainly that 2027 amounts are not yet published (checked against the Internal Revenue Bulletin and irs-drop on 2026-11-02).

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": {
      "tax_year": "<tax_year>"
    },
    "name": "get_tax_brackets_and_standard_deduction"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearYes2025 or 2026. 2027 returns a not-yet-published error.
filing_statusNoLeave out to get all filing statuses.
taxable_incomeNoTaxable income to compute tax on (needs filing_status).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: it names the legal provenance (One Big Beautiful Bill Act, Rev. Proc. 2025-32), documents a freshness check date against the Internal Revenue Bulletin and irs-drop, and states how unpublished years fail. That is exactly the trust and staleness context an agent needs for a tax-data lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, which is good, but the body is a dense run-on that inlines eight dollar figures per year plus provenance and a check date. The dollar amounts are return values that the response itself would carry, so much of this length is not load-bearing for tool selection.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so: it enumerates brackets, standard deductions per filing status, the age-65/blind add-on, and the optional tax and marginal-rate result. Nothing an agent needs to call it correctly or interpret the result is missing.

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 the schema already documents tax_year bounds, the filing_status enum, and that filing_status is required for the income computation. The description reinforces the optional computation behavior but adds no new syntax or constraint detail beyond that baseline.

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 official 2025 and 2026 federal income tax brackets and standard deductions,' plus an optional computation mode. This is clearly distinguishable from the calculate_* siblings, which are single-deduction calculators rather than a bracket/deduction reference with tax computation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by two described modes - fetch the bracket tables, or 'optionally computes the tax and marginal rate on a taxable income' when income is supplied. However, it never tells the agent when to prefer this tool over the calculate_* siblings, nor any exclusions beyond the 2027 'not yet published' case.

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.