Skip to main content
Glama

Custom Solutions

Maximum offer at a target cap rate

compute_max_offer_at_cap_rate
Read-onlyIdempotent

Most to pay for a rental so its NOI earns a target cap rate: NOI divided by the target, less the repairs and purchase costs the deal needs, with a floor of 0. Working backward from a cap rate is where offers go wrong, because the value at the target cap rate still has to pay for repairs and closing costs before it becomes a price. Send the stabilized yearly noi and target_cap_pct (8 means 8%); optionally repairs and purchase_costs. A negative NOI gives a maximum price of 0 with a flag.

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": {
      "noi": "<noi>",
      "target_cap_pct": "<target_cap_pct>"
    },
    "name": "compute_max_offer_at_cap_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
noiYesStabilized NOI per year, e.g. 28000
repairsNoRepairs the deal needs, e.g. 15000
purchase_costsNoClosing, inspection and other purchase costs, e.g. 4000
target_cap_pctYesTarget cap rate in percent, e.g. 8

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?

Annotations already cover the safety profile (read-only, idempotent, closed-world, non-destructive), and the description adds real behavior beyond them: the zero floor and the negative-NOI branch that returns 0 with a flag. What is missing is any statement about how repairs and purchase costs interact when they exceed the computed value, though the floor largely covers that.

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 formula leads, followed by the rationale and then the input/output contract, which is good front-loading. The middle sentence about where offers go wrong is editorial and could be trimmed, but it earns some of its space by motivating the repair and cost deductions.

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 four-parameter, annotation-covered, no-output-schema calculator, the description supplies the formula, required inputs, and the edge-case return value, which is enough to call it correctly. A note on rounding or units of the returned figure would close the last gap.

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 each parameter already carries an example, so the baseline is 3. The description confirms which two inputs are required and that repairs and purchase_costs are optional, plus the percent convention for target_cap_pct, but adds no format or unit detail the schema does not already give.

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?

Names a specific computation (max offer from NOI and a target cap rate) and spells out the exact formula, including the deduction of repairs and purchase costs and the zero floor. It is clearly the inverse of a cap-rate calculation, so an agent can distinguish it from compute_cap_rate without opening a 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?

Explains the situation it is built for — working backward from a cap rate to a price — and warns that this is where offers commonly go wrong. It does not explicitly name a sibling alternative or state when not to use it, so it falls short of a 5, but the context is clear.

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