Skip to main content
Glama

LeaseLine Rent Ledger

Calculate prorated rent

calculate_prorated_rent
Read-onlyIdempotent

Use this when the user wants prorated rent for a move-in or move-out (prorated rent calculator, 'tenant moved in on the 17th, how much rent do they owe', partial month rent). Returns the amount, computed to the cent, by three methods side by side (actual days in the month, 30-day month, 365-day year), the daily rate, and the formula, counting the move-in and move-out days inclusively; leap-year February is handled. Assumes rent covers calendar months (due on the 1st). Does not build a full ledger (use generate_rent_ledger for payments and balances) and does not give legal advice.

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>"
    },
    "name": "calculate_prorated_rent"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoThe proration method the lease uses; the result shows all three. actual_days (default): rent / days in that month. thirty_day: rent / 30. annual_365: rent x 12 / 365.
roundingNoround_total (default): round only the final amount to the cent. daily_rate_first: round the daily rate to the cent first, then multiply by the days.
monthly_rentYesFull monthly rent in USD, e.g. 1450.
move_in_dateNoMove-in date (first day the tenant has the unit), YYYY-MM-DD, e.g. 2026-10-17. Give this, move_out_date, or both.
move_out_dateNoMove-out date (last day the tenant pays for), YYYY-MM-DD, e.g. 2026-11-10.

Output Schema

NameRequiredDescriptionDefault
kindYes
notesYes
methodYes
displayYes
periodsYes
roundingYes
method_labelYes
monthly_rentYes
total_proratedYes
full_months_betweenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description goes further productively: it discloses the output shape (three methods side by side, daily rate, formula, cent precision), the inclusive day-counting rule, leap-year February handling, and the modeling assumption that rent covers calendar months due on the 1st. These are computational semantics an agent cannot get from annotations or schema.

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?

Single paragraph, front-loaded with the trigger and output contents, then assumptions, then exclusions — a sensible ordering with no filler. It is dense rather than bloated, though the parenthetical list of paraphrases is slightly redundant against the opening clause.

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 read-only calculation tool with full schema coverage, output schema, and complete annotations, the description closes the remaining gaps: modeling assumptions, edge cases (leap year, inclusive days), and sibling routing. An agent has everything needed to select and invoke it 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 and the schema already explains each method, rounding, and date field. The description adds interpretive value the schema lacks: that results are always shown for all three methods regardless of the selected one, that move-in and move-out days count inclusively, and that leap-year February is handled — factors that materially affect how an agent interprets the date parameters.

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 ('prorated rent for a move-in or move-out') and enumerates concrete user phrasings it answers. It is immediately distinguishable from the single sibling, generate_rent_ledger, which the description explicitly names as the different tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit trigger ('Use this when the user wants...') including example utterances, and closes with two exclusions that route elsewhere ('does not build a full ledger (use generate_rent_ledger...)', 'does not give legal advice'). Nothing about when-to-use or when-not is left to inference.

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