Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Lessee lease liability and ROU schedule

accounting-schedules_lease-schedule
Read-onlyIdempotent

Present-value a payment stream at the periodic discount rate and amortise the lease liability and right-of-use asset (IFRS 16 / ASC 842 finance-lease mechanics). Price $0.04 USDC. POST /api/v1/accounting-schedules/lease-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": {
      "payments": "<payments>",
      "commencement": "<commencement>",
      "discountRate": "<discountRate>"
    },
    "name": "accounting-schedules_lease-schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
timingNotiming, string, one of arrears, advance. Required.arrears
paymentsYespayments, array. Required.
incentivesNoincentives, integer, from 0 to 9007199254740991. Required.
periodicityNoperiodicity, string, one of annual, monthly. Required.annual
commencementYesdate, string, date. Required.
discountRateYesdiscountRate, number, from 0 to 1. Required.
initialDirectCostsNoinitialDirectCosts, integer, from 0 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
rouAssetNorouAsset. Number.
scheduleNoschedule. Array.
limitationsNolimitations. Array.
initialLiabilityNoinitialLiability. 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 readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds genuinely new behavioral context the annotations cannot express: a per-call price of $0.04 USDC, the POST endpoint, and crucially that an unpaid call returns x402 payment terms instead of executing. That last detail prevents an agent from misreading a payment-terms response as a computed schedule. No statement on what happens with malformed payment streams or how the schedule is keyed, which keeps it from a 5.

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 core computation is front-loaded in the first sentence, followed by cost, endpoint, and paywall behavior in short declarative sentences. Every sentence carries operational information. Minor overhead from spelling out the raw route, but nothing is padding.

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?

With an output schema present, the description need not explain return values, and it correctly focuses on the computation performed, the governing standards, the price, and the payment-gate failure mode. For a 7-parameter, fully schema-documented read-only computation, an agent has everything needed to decide and invoke 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 100%, so the baseline is 3. The description earns above that by clarifying that discountRate is the PERIODIC rate applied to the payment stream, which materially changes how an agent should populate a 0-1 number field relative to periodicity (annual vs monthly). It does not explain how incentives, initialDirectCosts, or timing (arrears/advance) alter the computation, leaving those to the schema.

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?

The description names specific operations (present-value a payment stream, amortise the lease liability and right-of-use asset) against a named resource and accounting regime (IFRS 16 / ASC 842). An agent can distinguish this from generic amortization siblings. It stops short of naming the nearest alternative (loan-amortization-journal or depreciation-schedule), so the boundary with those overlapping tools is left to inference.

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 by the standards reference (IFRS 16 / ASC 842 finance-lease mechanics), which tells an agent this is the lease-specific schedule builder rather than a general loan or depreciation tool. However, there is no explicit when-to-use / when-not-to-use statement and no sibling named as an alternative, which is a real gap given the crowded accounting-schedules family.

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