Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

US MACRS GDS depreciation

accounting-schedules_macrs-depreciation
Read-onlyIdempotent

Apply IRS Publication 946 Appendix A GDS percentage tables (half-year, mid-quarter, mid-month) after optional section 179 and caller-supplied bonus percentage. Price $0.03 USDC. POST /api/v1/accounting-schedules/macrs-depreciation. An unpaid call returns the x402 payment terms and does not run.

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>",
      "recoveryPeriod": "<recoveryPeriod>",
      "convention": "<convention>"
    },
    "name": "accounting-schedules_macrs-depreciation"
  }
}

Input Schema

NameRequiredDescriptionDefault
basisYesbasis, integer, from any to 9007199254740991. Required.
bonusPctNobonusPct, number, from 0 to 1. Required.
conventionYesconvention, string, one of HY, MQ, MM. Required.
section179Nosection179, integer, from 0 to 9007199254740991. Required.
monthPlacedNomonthPlaced, integer, from 1 to 12. Required.
q4BasisShareNoq4BasisShare, number, from 0 to 1. Optional.
quarterPlacedNoquarterPlaced, integer, from 1 to 4. Required.
recoveryPeriodYesrecoveryPeriod, value. Required.
placedInServiceNoplacedInService, string, date. Optional.

Output Schema

NameRequiredDescriptionDefault
rowsNorows. Array.
bonusNobonus. Number.
tableNotable. String.
sourcesNosources. Array.
section179Nosection179. Number.
limitationsNolimitations. Array.
depreciableBasisNodepreciableBasis. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful context beyond them: a fixed $0.03 USDC x402 price, the POST endpoint, and the important behavior that an unpaid call returns payment terms and performs no computation.

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?

Four short sentences, front-loaded with the computation before the commercial and transport details. Every sentence carries information; there is no filler, though the endpoint and price could be tightened.

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 nine parameters at full schema coverage and an output schema present, the description need not explain return values, and it correctly covers computation scope and payment gating. The remaining gap is that it never indicates which parameters are conditional on the chosen convention, which is the main source of misuse risk for this tool.

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 baseline is 3. The description does add a little meaning by naming 'optional section 179' and 'caller-supplied bonus percentage' (mapping bonusPct to a 0-1 fraction supplied by the caller) and by glossing HY/MQ/MM as half-year/mid-quarter/mid-month, but it says nothing about the conditional role of monthPlaced, quarterPlaced or q4BasisShare.

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: 'Apply IRS Publication 946 Appendix A GDS percentage tables' with the three conventions enumerated, plus the ordering of section 179 and bonus adjustments. This is precise enough to separate it from the generic accounting-schedules_depreciation-schedule sibling without opening either schema.

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?

Use is implied by the MACRS/GDS framing but the description never says when to pick this over the sibling depreciation-schedule tool, nor what inputs make a case ineligible (e.g. non-US tax basis, assets outside Pub 946 tables). No explicit when/when-not guidance is given.

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