Skip to main content
Glama

curatedapi

MACRS depreciation calculator (IRS tables, GDS)

calc_accounting_depreciation_macrs
Read-only

US tax depreciation under MACRS (GDS) with the IRS percentage tables, Section 179 and bonus depreciation.

Applies the Publication 946 Appendix A tables: half-year or mid-quarter for personal property (Tables A-1 to A-5), mid-month for residential rental (A-6, 27.5 years) and nonresidential real property (A-7a, 39 years). Section 179 comes off first, then bonus depreciation on what is left, then MACRS on the rest. Each year is basis × the table percentage, rounded; the last year takes whatever rounding left over, so the years add up exactly to the basis.

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": {
      "basis": "<basis>",
      "property_class": "<property_class>",
      "placed_in_service": "<placed_in_service>"
    },
    "name": "calc_accounting_depreciation_macrs"
  }
}

Input Schema

NameRequiredDescriptionDefault
basisYesDepreciable basis: the cost, plus costs to get the property ready, less any business-use reduction. Allowed: > 0 and <= 1000000000000000. Unit: currency.
optionsNoPrecision and rounding of the results (default: rounding=half_even, decimals=2).
conventionNoConvention for personal property. 27.5- and 39-year property always use mid-month, whatever is passed. Options: half_year: half a year of depreciation in the first year (the usual case); mid_quarter: when more than 40% of the year's basis was placed in service in the last quarterhalf_year
section_179NoSection 179 deduction taken for the property. The dollar limit and business-income limit are not checked. Allowed: >= 0 and <= 1000000000000000. Unit: currency.0
bonus_percentNoSpecial (bonus) depreciation percentage, e.g. 100 or 40, or 0 if you elect out. Allowed: >= 0 and <= 100. Unit: percent.0
property_classYesRecovery period (property class). Options: 3: 3-year property (200% declining balance); 5: 5-year property such as cars, computers and office machinery (200% DB); 7: 7-year property such as office furniture and fixtures (200% DB); 10: 10-year property (200% DB); 15: 15-year property such as land improvements (150% DB); 20: 20-year property such as farm buildings (150% DB); 27.5: 27.5-year residential rental property (straight line, mid-month); 39: 39-year nonresidential real property (straight line, mid-month)
placed_in_serviceYesThe day the property was placed in service.
tax_year_start_monthNoMonth your tax year starts (1 = calendar year). Short tax years are not supported. Allowed: >= 1 and <= 12.

Output Schema

NameRequiredDescriptionDefault
inputsYesThe inputs as understood.
resultYes
formulaNo
receiptNoOnly with ?receipt=true: a signed receipt for this answer, a JSON Web Token signed with Ed25519 (alg EdDSA). Its claims are iss, iat, jti (the request id), endpoint, date and response (this response without the receipt). Check it with the keys at /.well-known/jwks.json or POST /v1/receipts/verify.
warningsYes
exactnessYesFor each decimal output: exact; rounded (correctly, to the precision); rounded_uncertified (the last digit could not be proven); or underflow (below 1e-100, reported as 0).
precisionNoThe precision and rounding that were applied.
calculatorYesThe calculator and version that ran.
referencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, non-destructive, closed-world behavior, and the description still adds real substance: the fixed order of the 179 → bonus → MACRS reductions, per-year basis × table percentage, and the leftover-rounding rule that makes years sum exactly to basis. It does not restate that Section 179 dollar and business-income limits are unchecked (that lives only in the schema), which is the main behavioral caveat an agent might want surfaced here.

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

Conciseness5/5

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

Purpose is front-loaded in the first sentence, followed by table selection and then the calculation logic; every sentence adds information and none repeats the title or schema verbatim. It is dense but appropriately sized for an eight-parameter tax calculator.

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?

With an output schema present, the description correctly omits return-value details and instead spends its words on algorithm and table choice, which is what an agent needs. The only gap is that assumptions and limits (unchecked 179 caps, no short tax years) are left entirely to the schema rather than reinforced in prose.

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%, so the baseline is 3, but the description goes beyond field-by-field docs by explaining how basis, section_179 and bonus_percent compose ('Section 179 comes off first, then bonus depreciation on what is left, then MACRS on the rest'). That interaction is not obvious from the individual parameter descriptions and materially changes how an agent should set them.

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 names a specific verb and resource ('US tax depreciation under MACRS (GDS)') and pins the exact authority ('Publication 946 Appendix A tables'), which separates it cleanly from the sibling India depreciation calculators without needing to name them. An agent can tell from the first line that this is the US MACRS routine, not a generic or IFRS/ASC depreciation tool.

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?

It gives clear context for selection: half-year or mid-quarter for personal property, mid-month for 27.5/39-year property, and states that section 179 is applied before bonus before MACRS. What it lacks is any explicit exclusion or pointer to an alternative (e.g., when to prefer the India or straight-line siblings, or when mid-quarter must be used), so it sits below the top band.

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.

Resources