Skip to main content
Glama
Sign In

2027 Tax Brackets and Standard Deduction MCP

by io.github.theluckystrike
OverviewDiscussionsAdmin

Get 2027 standard deduction

get_standard_deduction
Read-onlyIdempotent

The standard deduction for tax year 2027 (or 2026) for a filing status from IRS Rev. Proc. 2026-35, with the additional amount for each filer who is 65 or older or blind, the dependent rule (greater of a floor or earned income plus a fixed amount), and the change from the other year.

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": {
      "filing_status": "<filing_status>"
    },
    "name": "get_standard_deduction"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_yearNoTax year, 2027 or 2026. Default 2027.
blind_countNoHow many filers are blind (0 to 2, joint returns only 2). Default 0.
earned_incomeNoEarned income of the dependent filer, used only when can_be_claimed_as_dependent is true.
filing_statusYes
age_65_or_older_countNoHow many filers are 65 or older by December 31 of the tax year (0 to 2, joint returns only 2). Default 0.
can_be_claimed_as_dependentNoTrue if someone else can claim this filer as a dependent. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already establish this as a read-only, idempotent, closed-world lookup, so the safety profile is covered. The description usefully adds provenance (IRS Rev. Proc. 2026-35) and enumerates what the response contains, including the dependent rule and the change from the other year, which is real value beyond annotations. It stops short of describing defaults, edge cases, or how the two-year comparison is presented.

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?

A single dense sentence that front-loads the resource, tax years, and source before enumerating the included components. There is no filler, though the clause-heavy structure makes it slightly harder to scan than a short bulleted breakdown would be.

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 must carry the return-value burden, and it does: it states the deduction amount, the per-filer additional amounts, the dependent computation rule, and the cross-year delta. Combined with the 83% schema coverage and read-only annotations, an agent has enough to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (83%), so the schema carries most parameter documentation. The description still adds meaning beyond it by spelling out the dependent rule (greater of a floor or earned income plus a fixed amount), which explains why earned_income and can_be_claimed_as_dependent exist and how they interact, and by framing the 65-or-older/blind inputs as additive amounts.

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

Purpose4/5

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

The description names a specific resource (standard deduction) and the exact computation inputs (filing status, tax year 2027/2026) plus what the result includes (age/blind additions, dependent rule, year-over-year change). It is clearly distinct from the tax-bracket and tax-calculation siblings, though it does not name them explicitly.

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 only implied: an agent can infer this is the tool for standard deduction figures rather than bracket or total-tax math. There is no explicit statement of when to prefer it over get_tax_amounts or calculate_federal_income_tax, and no prerequisites or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All 2027 Tax Brackets and Standard Deduction MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources