Skip to main content
Glama

LeaseLine Rent Ledger

Generate rent ledger

generate_rent_ledger
Read-onlyIdempotent

Use this when the user wants a rent ledger, tenant ledger, rent ledger template filled in, or proof of rent payments for a tenant: 'make a ledger of my tenant payments this year', 'tenant paid 800 of 1200 rent, what is the balance', amount due as of a date. Takes lease terms (rent, start, due day, late fee rule with grace period) and payments typed or from an attached CSV/Excel file; charges rent monthly with prorated first/last months, applies payments oldest first, adds late fees (flat, percent, daily with cap), carries overpayments forward as credit, and returns a running balance plus PDF statement, Excel and CSV downloads. Does not check state late-fee limits, give legal advice, collect rent, or make rent receipts for proof of address.

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": {
      "monthly_rent": "<monthly_rent>",
      "lease_start": "<lease_start>",
      "as_of_date": "<as_of_date>"
    },
    "name": "generate_rent_ledger"
  }
}

Input Schema

NameRequiredDescriptionDefault
late_feeNoLate fee rule from the lease, e.g. {"type": "flat", "amount": 75, "grace_days": 5}. Omit for no late fees.
paymentsNoPayments received from the tenant, e.g. [{"date": "2026-02-03", "amount": 1450}]. Payments before a due date become a credit.
propertyNoProperty or unit, e.g. 412 Oak St, Unit 2B, Austin, TX.
lease_endNoMove-out date (last day charged), YYYY-MM-DD, e.g. 2026-08-10. Omit for an ongoing tenancy.
as_of_dateYesStatement date: charges and payments up to and including this day, YYYY-MM-DD, e.g. 2026-10-03. Use the date the user names, otherwise today's date from the conversation (the user's local date).
lease_startYesLease start or move-in date, YYYY-MM-DD, e.g. 2026-01-17. A mid-month start is prorated when rent is due on the 1st.
tenant_nameNoTenant name shown on the statement, e.g. Maria Lopez. Do not include a Social Security number.
monthly_rentYesMonthly rent in USD from the lease, e.g. 1450.
rent_changesNoRent increases or decreases during the period, e.g. [{"effective_date": "2026-07-01", "monthly_rent": 1525}].
rent_due_dayNoDay of the month rent is due, 1-28, e.g. 1 (default).
landlord_nameNoLandlord or property manager name for the statement header, e.g. Oak Street Rentals LLC.
other_chargesNoCharges other than rent (utilities, pet rent, repair, returned check fee) and credits (concessions). Do not include the security deposit unless the user asks.
payment_orderNoHow payments are applied: oldest_first (default, oldest unpaid charge first, including late fees) or rent_first (rent and other charges before late fees).
payments_fileNoOptional CSV or Excel (.xlsx) list of payments with a date column and an amount column, e.g. payments-2026.csv.
proration_methodNoHow a partial first or last month is prorated: actual_days (default, rent / days in month), thirty_day (rent / 30), annual_365 (rent x 12 / 365).
proration_roundingNoround_total (default, round only the final amount to the cent) or daily_rate_first (round the daily rate to the cent before multiplying).

Output Schema

NameRequiredDescriptionDefault
kindYes
agingYes
as_ofYes
leaseYes
monthsYes
tenantYes
displayYes
summaryYes
propertyYes
warningsYes
downloadsYes
open_itemsYes
prorationsYes
rows_totalYes
recent_rowsYes
months_totalYes
payments_fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses key behavior: monthly rent charging, prorated first and last months, oldest-first payment application, late-fee types with caps and grace periods, overpayment credit carryforward, running balance, and PDF/Excel/CSV outputs. It also explicitly states what the tool does not do, such as checking state late-fee limits or giving legal advice.

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 description is front-loaded with the core use case and then summarizes behavior and exclusions. It is somewhat dense and long, but the length is justified by the tool's complexity and the number of computations it performs.

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?

Given the 16-parameter schema, full parameter descriptions, output schema, and annotations, the description is complete for correct invocation. It explains the computation model, expected inputs, outputs, and exclusions, leaving no significant ambiguity about what the tool will do.

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 every parameter is already well documented with formats, examples, defaults, and enums. The description adds helpful high-level context about lease terms, payments typed or from CSV/Excel, and proration, but it does not add materially new parameter semantics beyond what the schema already provides.

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 states a specific verb and resource: generating a rent ledger from lease terms and payments, with concrete examples such as tenant payment ledgers and balance-due statements. It is very clear what the tool produces, though it does not explicitly differentiate from the sibling calculate_prorated_rent tool, which overlaps on proration calculations.

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 strong 'use this when' guidance with example user utterances and clear exclusions such as no legal advice, no rent collection, and no proof-of-address receipts. It does not name an alternative tool or explain when to choose calculate_prorated_rent instead, so it falls just short of full when/when-not/alternatives coverage.

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