Skip to main content
Glama

Custom Solutions

Rent-raise turnover

compute_rent_raise_turnover
Read-onlyIdempotent

Expected move-outs and year-1 cost of raising below-market rents to market, under Custom Solutions' model from its Rental Property Portfolio Analyzer: the share of current tenants likely to leave, the make-ready cost per unit that turns over and the rent lost while those units sit empty. The figure is hard to estimate because move-outs rise with the size of the raise, with month-to-month tenancies and with the length of tenancy; the model's parameters are the firm's planning assumptions, listed in the answer. Send current_rent and market_rent per unit per month and units; optionally vacant_units, month_to_month_units and tenancy_years.

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": {
      "current_rent": "<current_rent>",
      "market_rent": "<market_rent>",
      "units": "<units>"
    },
    "name": "compute_rent_raise_turnover"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitsYesUnits in the property, e.g. 4
market_rentYesMarket rent per unit per month, e.g. 1450
current_rentYesAverage rent current tenants pay per unit per month, e.g. 1050
vacant_unitsNoUnits vacant now, e.g. 0
tenancy_yearsNoAverage years the current tenants have lived there, e.g. 9
month_to_month_unitsNoTenanted units with no lease, e.g. 2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare a safe, read-only, idempotent, closed-world computation, so the description does not need to restate that. It still adds real behavioral context: this is an output of Custom Solutions' Rental Property Portfolio Analyzer model, the parameters are the firm's planning assumptions, and those assumptions are listed in the answer, which tells the agent the numbers are model estimates rather than raw data.

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 outputs first, then the modeling rationale, then the inputs, which is a sensible order for an agent skimming it. The first two sentences are dense and long-winded, and the rationale sentence could be trimmed, but each part still carries information that is useful for calling the tool correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining the return value, and it does so: the share of tenants likely to leave, the make-ready cost per unit that turns over, and the rent lost while those units sit empty. It does not lay out the exact response structure, such as field names or whether a single net cost figure is produced, but it covers enough for a six-parameter calculator.

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 description coverage is 100%, so the schema already gives per-field examples; the baseline is therefore 3. The description goes beyond it by naming which inputs are required (current_rent, market_rent, units) and which are optional, by specifying units of measure ('per unit per month'), and by explaining the model logic that gives month_to_month_units and tenancy_years meaning, namely that move-outs rise with both.

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 computation: the expected share of move-outs and the year-1 cost of raising below-market rents to market, including make-ready cost and lost rent on vacant units. That is clearly distinct from the other compute_* siblings such as compute_cap_rate or compute_dscr, so an agent can tell what this tool produces 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 Guidelines3/5

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

Usage is only implied: the tool applies when a landlord is considering raising below-market rents, and the description frames why the estimate is hard (move-outs rise with the size of the raise, with month-to-month tenancies and with tenancy length). It never states when to prefer this over a sibling calculation or what the exclusions or prerequisites are, so the agent must infer the fit.

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