Skip to main content
Glama

Custom Solutions

Break-even occupancy

compute_break_even_occupancy
Read-onlyIdempotent

Break-even occupancy of a rental: the share of scheduled rent needed to pay operating expenses and debt service, and the cushion left above it. Over 100% means the property cannot cover its costs even fully rented. The common mistake is measuring against collected rent instead of scheduled rent, which hides the vacancy the figure exists to show. Send gross_rent_annual (scheduled rent at full occupancy), operating_expenses_annual and, when there is a loan, annual_debt_service; with no debt service the figure covers operating expenses only.

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": {
      "gross_rent_annual": "<gross_rent_annual>",
      "operating_expenses_annual": "<operating_expenses_annual>"
    },
    "name": "compute_break_even_occupancy"
  }
}

Input Schema

NameRequiredDescriptionDefault
gross_rent_annualYesScheduled rent per year at full occupancy, e.g. 36000
annual_debt_serviceNoPrincipal and interest per year, e.g. 12000 (0 for no loan)
operating_expenses_annualYesOperating expenses per year, e.g. 14000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, closed-world safety profile, so the bar is lower. The description adds real value beyond them: the >100% interpretation threshold, the debt-service-optional behavior, and the caveat about scheduled vs collected rent, though it does not state the return format or units of the result.

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 definition, then the failure mode, then the input instructions. Every sentence carries content, though the 'common mistake' sentence is slightly digressive for a tool that only computes a number.

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?

For a three-parameter read-only computation with full schema coverage and no output schema, the definition supplies the formula logic, edge-case handling, and input guidance an agent needs. Only the shape of the returned value (percentage vs ratio, units) is left unspecified.

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 baseline is 3, and the description goes further by restating the semantic distinction that matters most: gross_rent_annual is scheduled rent at full occupancy, not collected rent. It also clarifies the no-loan case for annual_debt_service, adding meaning beyond the schema.

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 the specific metric and its formula components: 'the share of scheduled rent needed to pay operating expenses and debt service, and the cushion left above it.' It also names the boundary condition (over 100% = cannot cover costs), which distinguishes it clearly from siblings like compute_dscr or compute_noi.

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?

Explains what inputs to send and the conditional case ('when there is a loan... with no debt service the figure covers operating expenses only'), plus a warning against the common mistake of using collected rent. It gives clear context but does not explicitly name a sibling alternative to use instead.

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