Skip to main content
Glama

Pad Count: mobile home park loan sizer

Which loans fit a mobile home park, and how much

size_park_loan
Read-onlyIdempotent

Runs the Pad Count loan sizer on one mobile home park: for Fannie Mae MHC, Freddie Mac MHC, HUD 223(f) MHC and the user's own bank or CMBS terms it returns a verdict (fits, check first, doesn't fit), the loan amount (the smaller of value x max LTV and NOI / (coverage x loan constant)), which limit binds, the rate used (Treasury for the term plus a spread) and every published rule the park fails. SBA 7(a) and 504 come back as not eligible, with the SOP quote.

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": {
      "pads": "<pads>",
      "occupied_pads": "<occupied_pads>",
      "noi": "<noi>",
      "value": "<value>"
    },
    "name": "size_park_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
noiYesNet operating income in dollars per year, after management and reserves, e.g. 268000. value_park_on_lot_rent can build it.
padsYesTotal pads (sites) in the park, e.g. 80.
valueYesPurchase price, or value if refinancing, in dollars, e.g. 3460000.
purposeNoPurchase or refinance. Default purchase.purchase
borrowerNoBorrower type: private, resident_owned (ROC or co-op), nonprofit, government (state or local), cdfi or tribe. Default private.private
spread_pctNoSpread over Treasury in percent. Default 2.00, which is an example, not a quote.
term_yearsNoLoan term in years: 5, 7 or 10. Picks the Treasury yield and Freddie Mac's LTV tier. Default 10.
loan_wantedNoOptional loan amount wanted, in dollars; each program says whether it covers it.
homes_on_siteNoEvery home in the park, empty or not. Defaults to occupied_pads.
occupied_padsYesOccupied pads, e.g. 68. Capped at total pads.
quality_levelNoFannie Mae quality level from the lender's inspection, 1 to 5; 0 = not known (default).
current_balanceNoRefinance only: current loan balance in dollars (HUD 223(f) here allows no cash out). Default 0.
own_lender_dscrNoYour lender's minimum debt service coverage, e.g. 1.30. Default 1.30 (an example).
park_owned_homesNoHomes owned by the borrower, an affiliate or an outside investor. Default 0.
owns_another_parkNoWhether the key principal owns at least one other park (Freddie Mac requires it). Omit if not known.
own_lender_ltv_pctNoYour bank or CMBS lender's max LTV in percent. Default 70 (an example; banks publish no single term).
years_park_experienceNoYears the key principal has owned or run parks (Freddie Mac needs 2+). Omit if not known.
own_lender_amortization_yearsNoYour lender's amortization in years. Default 25 (an example).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds substantial behavioral detail beyond annotations: the verdict categories, the loan amount formula, which limit binds, the rate construction, failed rules, and the SBA SOP quote.

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 action and then packs in return details. It is dense and slightly run-on, but every clause contributes useful information about outputs or scope.

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 complex 18-parameter tool with no output schema, the description explains the return values, program coverage, SBA exclusion, and sizing formula. Combined with the fully documented input schema and safety annotations, it is complete enough for an agent to call 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%, so the schema already documents all 18 parameters thoroughly. The description adds conceptual context around value, LTV, NOI, coverage, and loan constant, but does not add parameter-specific meaning beyond the schema.

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: it runs the Pad Count loan sizer on one mobile home park and returns a verdict plus loan details. It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as get_mhc_loan_program_rules or value_park_on_lot_rent.

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

Usage Guidelines3/5

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

Usage is implied by 'on one mobile home park' and by the note that SBA 7(a) and 504 come back as not eligible. However, there is no explicit guidance on when to choose this tool over the sibling rules or valuation tools.

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