Skip to main content
Glama
Sign In

FactLot

by io.github.9mp96ygnbk-alt
OverviewDiscussionsAdmin

Lease critical dates

calc_critical_dates
Read-onlyIdempotent

Dated list of a lease's notice deadlines and option windows, from its expiration date and options: each renewal option's notice deadline or notice window and renewal term (successive options count back from the term before), each termination option's last day to give notice, an expansion option deadline, and other deadlines (a stated date, or N days after a date such as a ROFO notice). Calendar months; N months before a date keeps the day of month, clamped to a shorter month's end (a warning gives the month-end reading when it is later). Deadlines on a weekend or US federal holiday (5 U.S.C. §6103, observed days included) are flagged, or rolled to the preceding or following business day when business_day_roll says so. With as_of: days to each event, passed deadlines warned, and the next deadline. Steps show each computation. Deterministic: use this instead of doing the math yourself; cite formula calc.critical_dates@1 and the returned steps, and surface any warnings.

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": {
      "expiration_date": "<expiration_date>"
    },
    "name": "calc_critical_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofNoDate to measure from (YYYY-MM-DD), usually today. Deadlines before it are flagged as passed; next_deadline is the first one on or after it.
holidaysNoHolidays that are not business days: "us_federal" (the eleven US federal holidays of 5 U.S.C. §6103(a), with the federal observed day when one falls on a weekend) or "none" (weekends only).us_federal
renewal_optionNoRenewal options, as lease.renewal_option states them: each is exercised by notice counted back from the expiration in effect when it is exercised.
expiration_dateYesExpiration date of the current term (YYYY-MM-DD), as the lease or the latest amendment states it.
other_deadlinesNoOther deadlines: expansion rights, ROFO or ROFR response periods, contraction rights.
business_day_rollNoWhat to do with a deadline that falls on a weekend or holiday: "none" (default) keeps the date and flags it; "preceding" moves it to the business day before (never later than the lease date: the safe choice); "following" moves it to the next business day, which only a lease clause that says so allows.none
commencement_dateNoCommencement date (YYYY-MM-DD). Optional; listed as an event and checked to be before expiration_date.
termination_optionsNoEarly termination options, as lease.termination_option states them; notice counts back from each effective_date.
expansion_option_deadlineNoLast day to exercise an expansion option (lease.expansion_option_deadline), YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish a read-only, idempotent, deterministic computation, and the description reinforces rather than contradicts that while adding substantive behavior: month-end clamped calendar arithmetic, warning emission, weekend/federal-holiday flagging vs. rolling, and step-by-step output. It also discloses that passed deadlines are warned and a next deadline is surfaced when as_of is given.

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?

It is front-loaded with the deliverable and reads as a single dense block with heavy parenthesis nesting, which slightly taxes scanning. Some holiday/statute detail duplicates what the schema already carries, but the substantive sentences all earn their place.

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 nine-parameter nested calculator with no output schema, the description compensates by describing return contents — per-event day counts, next deadline, warnings, and computation steps. Combined with the annotations, an agent has enough to call this correctly and report results.

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 goes beyond field text by explaining the succession rule (each renewal counts back from the term in effect before it) and the month-end clamping caveat with its warning. The only gap is that a few parameters, such as commencement_date's role, are only lightly touched.

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?

The description names a specific deliverable — a dated list of a lease's notice deadlines and option windows — and enumerates the classes it covers (renewal, termination, expansion, other). That is distinguishable at a glance from calc_rent_schedule, calc_lease_remeasurement_asc842, or calc_renew_vs_relocate 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?

It gives an explicit use directive: "Deterministic: use this instead of doing the math yourself," plus a citation instruction and a warning-surfacing instruction. It does not name sibling calculators or state when a different calc tool would be the better call, so the routing guidance stops at 'use this rather than hand math.'

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