Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Book depreciation schedule

accounting-schedules_depreciation-schedule
Read-onlyIdempotent

Straight-line, declining-balance, sum-of-years'-digits and units-of-production depreciation schedules with optional first-year convention and journal entries. Price $0.03 USDC. POST /api/v1/accounting-schedules/depreciation-schedule. 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": {
      "cost": "<cost>",
      "salvage": "<salvage>",
      "lifeYears": "<lifeYears>",
      "method": "<method>",
      "inServiceDate": "<inServiceDate>"
    },
    "name": "accounting-schedules_depreciation-schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYescost, integer, from any to 9007199254740991. Required.
methodYesmethod, string, one of SL, DDB, DB150, SYD, UOP. Required.
salvageYessalvage, integer, from 0 to 9007199254740991. Required.
lifeYearsYeslifeYears, integer, from any to 100. Required.
conventionNoconvention, string, one of full_month, half_year, none. Required.none
switchToSLNoswitchToSL, boolean. Required.
unitsTotalNounitsTotal, value. Optional.
inServiceDateYesinServiceDate, string, date. Required.
unitsByPeriodNounitsByPeriod, value. Optional.
fiscalYearEndMonthNofiscalYearEndMonth, integer, from 1 to 12. Required.

Output Schema

NameRequiredDescriptionDefault
entriesNoentries. Array.
periodsNoperiods. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive behavior, and the description adds genuinely new operational context: a $0.03 USDC price, the endpoint, and the x402 rule that an unpaid call returns payment terms instead of running. This payment-gating behavior is not inferable from any structured field. It does not describe the returned payload shape, though an output schema exists to cover that.

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?

Three tight sentences: capability first, price and endpoint second, payment gating last. Every sentence carries information, though the endpoint token duplicates structured routing data and could be trimmed.

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?

For a 10-parameter computational tool with an output schema, the description covers capability, method families, cost, and the payment precondition an agent must know before calling. The one uncovered linkage is that the UOP method depends on unitsTotal/unitsByPeriod, but the schema's parameter descriptions carry that adequately.

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 earns credit by expanding the opaque enum codes — SL, DDB, DB150, SYD, UOP — into their accounting names (straight-line, declining-balance, sum-of-years'-digits, units-of-production), which the schema does not do. It also signals that the first-year convention is optional, clarifying a field the schema marks with a default but that appears in the required list.

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?

States the specific resource (depreciation schedules) and enumerates the four supported methods plus optional convention and journal entries, which is a concrete verb-free but content-rich purpose. It does not explicitly distinguish itself from the sibling accounting-schedules_macrs-depreciation (tax vs book), leaving that differentiation implicit in the title.

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: book depreciation scheduling, as opposed to the MACRS sibling. There is no explicit when-to-use/when-not-to-use statement or named alternative, so the agent must infer selection from the title and method list.

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