Skip to main content
Glama

BRAINIAC Property Intelligence

Calculate rent yield

property-intelligence_rent-yield-calculate
Read-onlyIdempotent

Divide the supplied annual rent by the supplied price. Monthly rent is multiplied by 12 only when the period is month. The result is not a valuation. Price $0.03 USDC. POST /api/v1/property-intelligence/rent-yield-calculate. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "property-intelligence_rent-yield-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNourl, string, length 8 to 2000. Optional.
rentNorent, number, from 0 to 1000000000000. Optional.
textNotext, string, length 1 to 20000. Optional.
priceNoprice, number, from 0 to 1000000000000. Optional.
titleNotitle, string, length 1 to 200. Optional.
addressNoaddress, string, length 1 to 300. Optional.
depositNodeposit, number, from 0 to 1000000000000. Optional.
bedroomsNobedrooms, integer, from 0 to 100. Optional.
currencyNocurrency, string. Optional.
latitudeNolatitude, number, from -90 to 90. Optional.
bathroomsNobathrooms, number, from 0 to 100. Optional.
longitudeNolongitude, number, from -180 to 180. Optional.
rentPeriodNorentPeriod, string, one of month, year. Optional.
annualCostsNoannualCosts, number, from 0 to 1000000000000. Optional.
descriptionNodescription, string, length 1 to 20000. Optional.
floorAreaSqmNofloorAreaSqm, number, from any to 1000000. Optional.
mortgageRateNomortgageRate, number, from 0 to 1. Optional.
propertyTypeNopropertyType, string, length 1 to 80. Optional.

Output Schema

NameRequiredDescriptionDefault
rentNorent. Number.
priceNoprice. Number.
currencyNocurrency. String.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
annualRentNoannualRent. Number.
grossYieldNogrossYield. Number.
rentPeriodNorentPeriod. String.
limitationsNolimitations. Array.
officialValuationNoofficialValuation. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts: the call costs $0.03 USDC, is a POST to a specific endpoint, and an unpaid invocation returns x402 payment terms without executing. That payment-gating behavior is exactly the kind of thing an agent must know before calling.

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?

Four short sentences, front-loaded with the formula, then the unit rule, then cost/transport/payment behavior. Every sentence carries information; the endpoint path is the least valuable line but still aids invocation.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and payment behavior is covered. However, the tool accepts 18 optional parameters and the description accounts for only rent, price and rentPeriod, leaving an agent unable to tell whether deposit, annualCosts, mortgageRate or the listing-metadata fields influence the result or are simply ignored.

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 goes further by explaining the semantic effect of rentPeriod — monthly rent is multiplied by 12 only when the period is 'month' — which is the one enum whose behavior the schema cannot express. It still says nothing about the other numeric fields (deposit, annualCosts, mortgageRate).

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?

States a specific operation with the exact formula: annual rent divided by price, with the month-to-year conversion rule spelled out. An agent knows precisely what comes out. It does not name a sibling to differentiate from (e.g. investment-metrics), so it stops short of a 5.

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

Usage Guidelines2/5

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

The description implies you need rent and price, but never says when to pick this tool over investment-metrics or the other analysis siblings, nor what preconditions apply. The only scope hint is the negative caveat 'The result is not a valuation', which is not usage guidance.

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