opentax

compute_form_4562

Form 4562 — depreciation for an individual's businesses and rentals, tax years 2025-2027 (calendar year): § 179 expensing with the dollar limit, phase-out, married-filing-separately split, business income limitation and carryover; the § 168(k) special allowance (100% for property acquired after January 19, 2025; 40% in 2025 and 20% in 2026 for property acquired earlier; the TY2025 40% election; election out by class); MACRS with the printed Publication 946 tables (half-year, mid-quarter by the 40% test, mid-month for buildings; 150% DB, straight-line and ADS elections); dispositions during the year; listed property and the § 280F passenger automobile limits (2025 and 2026); and Rev. Proc. 87-56 asset classes for cost segregation (assetClass, e.g. '57.0', '00.11', '00.3'). Give EVERY asset in service: current-year assets with cost, placedInService and acquiredOn (the binding-contract date, which sets the bonus percentage); earlier assets also with convention (HY/MQ), section179Taken and specialAllowanceTaken. section179BusinessIncome is required when § 179 is elected or carried over (taxable income from actively conducted businesses including wages, without § 179, the half-SE-tax deduction or any NOL). Returns the form's lines, each asset's schedule, and the deduction by activity (Schedule C line 13, Schedule E line 18) — subtract each activity's amount from that business's income before depreciation. Situations the sources don't settle (short years, general asset accounts, 100% bonus on a passenger car, § 280F recapture, a disposition in the last recovery year) refuse with the reason. Report the lines and notes verbatim; dollars in, whole dollars out.

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": {
      "taxYear": "<taxYear>",
      "filingStatus": "<filingStatus>",
      "assets": "<assets>"
    },
    "name": "compute_form_4562"
  }
}

Input Schema

Name	Required	Description
`assets`	Yes
`taxYear`	Yes	2025, 2026 or 2027
`filingStatus`	Yes
`section179FromK1`	No	§ 179 expense allocated on Schedules K-1
`section179Carryover`	No	line 10: last year's line 13
`mfsAllocationPercent`	No
`spouseSection179Cost`	No	MFS: cost of § 179 property your spouse placed in service
`elect40PercentFor2025`	No
`section179BusinessIncome`	No	dollars, e.g. 50000 or "1234.56"
`electOutOfSpecialAllowance`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations at all, the description carries the full burden and does so thoroughly: it discloses the return payload ('the form's lines, each asset's schedule, and the deduction by activity'), the output conventions ('dollars in, whole dollars out', 'report the lines and notes verbatim'), a downstream instruction ('subtract each activity's amount from that business's income before depreciation'), and an explicit refusal contract for unsettled situations (short years, general asset accounts, 100% bonus on a passenger car, § 280F recapture, disposition in the last recovery year). That is unusually complete behavioral disclosure for a calculator.

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?

The scope statement is front-loaded correctly, but the body is a single dense run-on paragraph whose first sentence is a sprawling rule list inside parentheses. The content mostly earns its place given the domain complexity, yet the lack of sentence breaks or structure makes it hard to scan for the invocation-relevant instructions buried at the end.

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?

There is no output schema, but the description explains the return shape, per-asset schedule, and per-activity totals, and it documents per-asset requirements (current vs. earlier-year assets) plus refusal behavior. For a 10-parameter, highly technical form computation, an agent has everything needed to call it 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 only 50%, so the description has to compensate, and it largely does: it defines acquiredOn as the binding-contract date driving the bonus percentage, spells out that section179BusinessIncome means taxable income from actively conducted businesses including wages (without § 179, half-SE-tax, or NOL), gives assetClass examples ('57.0', '00.11', '00.3'), and explains the MFS split, carryover, and election-out semantics. Gaps remain for businessUsePercent, adsRecoveryPeriod, longProductionPeriod, and section179QualifiedRealProperty, which get no explanation in either place.

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 opening names the exact artifact and scope: 'Form 4562 — depreciation for an individual's businesses and rentals, tax years 2025-2027 (calendar year)'. This is unmistakably a Form 4562 depreciation computation and cannot be confused with siblings like calculate_tax, compute_return, or compute_form_2210.

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 rather than stated: the scope sentence and the instruction 'Give EVERY asset in service' tell the agent what inputs are expected, but nothing says when to reach for this tool versus compute_return or calculate_business_tax, and no exclusions are named. The prerequisite for section179BusinessIncome is the only conditional guidance offered.

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

All opentax tools Inspect

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

Need Help?