Skip to main content
Glama
Sign In

FactLot

by io.github.9mp96ygnbk-alt
OverviewDiscussionsAdmin

Lease remeasurement (ASC 842, lessee)

calc_lease_remeasurement_asc842
Read-onlyIdempotent

Remeasure a lessee's lease liability and right-of-use asset under ASC 842 after a modification, lease-term reassessment, contingency resolution, or residual value guarantee change: new liability (PV of remaining payments), liability and ROU adjustments with any gain (ASC 842-20-35-4), and the per-period amortization table (operating: straight-line single lease cost; finance: interest plus amortization) in cents that foots: every row rolls forward exactly, totals are the row sums, and the final period trues up liability and ROU asset to zero. Warns where judgment is needed. Deterministic: use this instead of doing the math yourself; cite formula calc.lease_remeasurement_asc842@2 and the returned steps, and surface any warnings.

Input Schema

NameRequiredDescriptionDefault
eventYesWhat triggered the remeasurement: modification_extend_term / modification_shorten_term / modification_change_in_payments (a modification not accounted for as a separate contract, ASC 842-10-25-8 and 25-11), reassessment_of_term_or_option (ASC 842-10-35-1 and 35-4(c)), contingency_resolved (variable payments became fixed, ASC 842-10-35-4(b)), residual_value_guarantee_change (ASC 842-10-35-4(c)(3)), or index_or_rate_change (ASC 842-10-35-4: not a remeasurement trigger by itself; computed as if remeasured for another reason).
paymentsYesRemaining lease payments after the event, in ascending period order. Periods not listed carry no payment (rent-free).
classificationYesLessee classification (ASC 842-10-25-2): operating (single straight-line lease cost) or finance (interest on the liability plus straight-line ROU amortization).
payment_timingNoWhether each payment falls at the beginning (in advance) or end (in arrears) of its period.end
liability_beforeYesCarrying amount of the lease liability immediately before the remeasurement, USD.
periods_per_yearNoPayment periods per year (12 for monthly, 4 for quarterly).
rou_asset_beforeYesCarrying amount of the right-of-use asset immediately before the remeasurement, USD (after any impairment).
remaining_periodsNoRemaining lease term in periods after the event. Defaults to the last period index in payments; set it higher when the final periods are rent-free.
discount_rate_annualYesAnnual discount rate applied to the remaining payments, e.g. 0.06. Nominal: the periodic rate is this ÷ periods_per_year.
discount_rate_updatedYesTrue when discount_rate_annual was determined at the remeasurement date (ASC 842-10-35-5: required for modifications and lease-term or purchase-option reassessments); false when it is the rate from commencement (kept for contingency resolutions and residual value guarantee changes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond them: deterministic output, the exact deliverables (new liability, liability/ROU adjustments with any gain, per-period amortization table), footing guarantees ('every row rolls forward exactly', 'final period trues up liability and ROU asset to zero'), and the presence of judgment warnings.

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?

Purpose and triggers are front-loaded in the opening clause, and every subsequent clause adds information (outputs, footing guarantees, citation requirement). It is a single dense semicolon-chained sentence, which is slightly heavy to parse but contains no filler.

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?

For a 10-parameter computational tool with no output schema, the description compensates by describing the return payload (liability, ROU adjustment, gain, amortization table), its units, its arithmetic invariants, and the warning behavior. An agent has everything needed to call it and interpret results.

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% with detailed ASC citations per field, so the schema carries parameter meaning. The description adds only marginal detail (output denominated in cents versus USD inputs) and otherwise does not elaborate on parameters. Baseline 3 is appropriate.

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 ('Remeasure a lessee's lease liability and right-of-use asset under ASC 842') and enumerates the four triggering events. An agent can distinguish it from siblings like calc_rent_schedule or calc_lease_vs_own without opening the schema.

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?

Gives clear when-to-use context via the trigger list (modification, term reassessment, contingency resolution, RVG change) and an explicit directive ('use this instead of doing the math yourself'). It does not name a sibling tool as the alternative for adjacent cases, so it stops short of full routing guidance.

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

All FactLot toolsInspect
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