Skip to main content
Glama
tresor4k

statetakehome-mcp

by tresor4k

Capital Gains Tax Calculator

capital_gains_tax

Compute federal capital gains tax including Net Investment Income Tax and optional state income tax for 2026. Input gain, ordinary taxable income, filing status, and term for estimates.

Instructions

Computes federal capital gains tax (long-term 0%/15%/20% stacked bands or short-term ordinary rates), the 3.8% Net Investment Income Tax (NIIT) above the MAGI threshold, and an optional state income tax on the gain (states generally tax capital gains as ordinary income). Example input: { "gain": 50000, "ordinaryTaxableIncome": 80000, "filingStatus": "single", "term": "long" }. 2026 tax year — estimates, not tax advice; thresholds from Rev. Proc. 2025-32, cross-checked against Tax Foundation & Schwab.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gainYesGross capital gain in USD (sale price minus cost basis), e.g. 50000.
termYes"long" for assets held > 1 year (preferential rates), "short" for ordinary rates.
stateNoOptional two-letter US state or DC postal code; most states tax the gain as ordinary income.
exclusionNoAmount excluded from the gain before tax (e.g. the §121 primary-residence sale exclusion).
filingStatusYesIRS filing status.
ordinaryTaxableIncomeYesOther taxable income (excluding the gain), which sets the long-term capital gains bracket and NIIT threshold.
Behavior4/5

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

No annotations are provided, so the description carries full burden. It indicates the tool computes estimates and is not tax advice, but does not explicitly state it is read-only or non-destructive. Implicitly, it is a calculator with no side effects.

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 description is a single dense sentence that packs all necessary information. While efficient, it could be slightly restructured for readability, but it earns its place without excess.

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

Completeness3/5

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

Given the tool's complexity (multiple tax components, optional state tax) and lack of output schema, the description does not specify the output format or breakdown. It covers inputs well but leaves output details unclear.

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 100%, providing baselines of 3. The description adds value by providing an example input and clarifying the 'gain' parameter as gross gain. It also mentions the §121 exclusion, adding context beyond the schema.

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 clearly states the tool computes federal capital gains tax, NIIT, and optional state tax, and distinguishes itself from sibling tools (us_take_home_pay, self_employment_tax) by focusing on capital gains specifically.

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?

The description includes an example input and specifies the tax year (2026) and that it provides estimates, not advice. It lacks explicit 'when to use' vs. alternatives, but the tool name and context make it clear for capital gains situations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/statetakehome-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server