FactLot

CAM reconciliation for every tenant (batch)

calc_cam_reconciliation_batch

Read-onlyIdempotent

Reconcile CAM for a whole building in one call: the expense pool and gross-up once, then up to 500 tenants each with share, base year or expense stop, cap, admin fee, occupancy, estimates paid, and lease-specific excluded categories. Returns each tenant's statement (identical to calc_cam_reconciliation for that tenant, with its trace and warnings) and a building reconciliation: total billed against the recoverable pool, the unrecovered amount, and why (unleased or vacant share, lease exclusions, gross-up, caps, base years and stops, admin fees, zero floor, rounding). Deterministic: use this instead of doing the math yourself; cite formula calc.cam_reconciliation_batch@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": {
      "year": "<year>",
      "expenses": "<expenses>",
      "tenants": "<tenants>"
    },
    "name": "calc_cam_reconciliation_batch"
  }
}

Input Schema

Name	Required	Description
`year`	Yes	Calendar or lease year being reconciled.
`tenants`	Yes	Every tenant to reconcile (up to 500): each one's share, structure (base year or stop), cap, admin fee, occupancy, estimates paid, and lease-specific exclusions. Each statement equals calc_cam_reconciliation for that tenant.
`expenses`	Yes	The building's operating expense pool for the year, entered once for every tenant: category, amount, controllable, recoverable, variable, admin_fee_applies.
`gross_up`	No	Gross up variable expenses to the target occupancy when actual occupancy is lower. Omit if the lease has no gross-up.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 7, 2026

changedInput schema / properties / expenses / items / properties / controllable / description

Previous value: -"Subject to the cap. Taxes, insurance, and utilities are typically uncontrollable."New value: +"Subject to the cap. Taxes, insurance, and utilities are typically uncontrollable. Default true; under a cap, lines left unset are named in warnings."

changedInput schema / properties / expenses / items / properties / variable / description

Previous value: -"Varies with occupancy, so eligible for gross-up (janitorial, utilities, management fee)."New value: +"Varies with occupancy, so eligible for gross-up (janitorial, utilities, management fee). Default false; with a gross-up, lines left unset are named in warnings."

AddedNov 4, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower, but the description still adds real context: determinism, that per-tenant statements carry a trace and warnings, and that a building-level reconciliation reports billed vs. recoverable pool and the reason for the unrecovered amount. The only gap is it doesn't say what happens on invalid input (e.g., an excluded category that doesn't match an expense line), despite the schema hinting at 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?

Front-loaded with the core action and scope, then the return shape, then the determinism directive. It is dense in a single paragraph and the field enumeration partially duplicates the schema, but no sentence is filler and the most decision-relevant facts come first.

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 no output schema, the description carries the burden of describing returns, and it does: per-tenant statements with trace and warnings, plus a building reconciliation of total billed against the recoverable pool, the unrecovered amount, and the enumerated causes. Given the deeply nested tenant/expense schema, this is complete enough for an agent to call it correctly.

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% and the nested objects are documented in depth, so the baseline applies. The description largely recaps the schema's field list (share, base year or stop, cap, admin fee, occupancy, estimates paid, excluded categories) without adding interpretation beyond what the schema already states.

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 plus scope: 'Reconcile CAM for a whole building in one call', with the expense pool and gross-up computed once for up to 500 tenants. It explicitly distinguishes itself from the single-tenant sibling by promising each statement is 'identical to calc_cam_reconciliation for that tenant', so an agent can route without opening either 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 a clear directive: 'Deterministic: use this instead of doing the math yourself', plus the citation requirement 'formula calc.cam_reconciliation_batch@1'. What's missing is explicit routing against the other CAM-related siblings in the list (calc_cam_reconciliation for one tenant, but also calc_reconcile_cam), leaving partial ambiguity about which CAM entry point to pick.

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

All FactLot tools Inspect

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.