Skip to main content
Glama

Custom Solutions

Cap rate

compute_cap_rate
Read-onlyIdempotent

Capitalization rate of a property: yearly NOI divided by the purchase price, as a ratio and a percent, with the most to pay for a target cap rate and the monthly rent-to-price ratio when those inputs are sent. A cap rate is only as good as its NOI: a monthly figure sent as yearly, or NOI after the mortgage, gives a number that looks plausible and is wrong by a factor of twelve or more, so the answer flags a cap rate over 25% and rent over 3% of price. Send noi (per year, may be negative) and price; optionally target_cap_pct and monthly_rent. A price of 0 is refused by name.

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>",
      "price": "<price>"
    },
    "name": "compute_cap_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
noiYesNet operating income per year, in dollars, e.g. 28000
priceYesPurchase price, e.g. 400000
monthly_rentNoScheduled rent per month, e.g. 3200, for the rent-to-price ratio
target_cap_pctNoTarget cap rate in percent, e.g. 8, for the most to pay at that rate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare a safe idempotent read, and the description adds substantial behavior on top: it names the two plausibility flags (cap rate over 25%, rent over 3% of price), discloses that negative NOI is accepted, and states that a price of 0 is refused by name. It also corrects the most common input error (monthly NOI or post-mortgage NOI) with the magnitude of the resulting mistake, which is exactly the kind of context annotations cannot carry.

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 and required inputs are front-loaded and every sentence carries information. The middle sentence is long and packs the NOI warning, the two flag thresholds, and the input list together, which is dense but still readable; minor trimming of the capitalization/unit restatement would tighten it.

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?

There is no output schema, so the description must convey what comes back, and it does: a ratio and a percent, an optional most-to-pay figure, an optional rent-to-price ratio, plus warning flags and a named refusal for price=0. For a four-parameter pure calculator with full annotation coverage, nothing an agent needs in order to call it correctly is missing.

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 the baseline is 3, but the description adds real meaning: noi is explicitly annual and may be negative, target_cap_pct drives the most-to-pay output, and monthly_rent drives the rent-to-price ratio. That maps each optional parameter to the output it activates, which the schema alone does not do.

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 gives a precise verb-and-resource definition – cap rate as yearly NOI divided by purchase price, returned as a ratio and a percent – plus the two derived outputs (most-to-pay at a target cap rate, rent-to-price ratio). It is immediately clear what the tool computes. It does not name or differentiate itself from siblings like compute_noi or compute_max_offer_at_cap_rate, which overlap with its inputs and one of its outputs.

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?

It explicitly tells the agent which inputs to send ('Send noi (per year, may be negative) and price; optionally target_cap_pct and monthly_rent'), which is direct invocation guidance. What is missing is routing advice: no statement of when to prefer this over compute_noi or compute_max_offer_at_cap_rate, even though it partially duplicates both.

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