Skip to main content
Glama

BRAINIAC Property Intelligence

Calculate investment metrics

property-intelligence_investment-metrics
Read-onlyIdempotent

Calculate net yield, price per square metre, loan, and cash flow only from supplied price, rent, costs, deposit, and mortgage rate. No loan-to-value is assumed. Price $0.04 USDC. POST /api/v1/property-intelligence/investment-metrics. 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_investment-metrics"
  }
}

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
loanNoloan. Number.
priceNoprice. Number.
currencyNocurrency. String.
findingsNofindings. Array.
netYieldNonetYield. Number.
checkedAtNocheckedAt. String.
annualRentNoannualRent. Number.
grossYieldNogrossYield. Number.
assumptionsNoassumptions. Array.
limitationsNolimitations. Array.
pricePerSqmNopricePerSqm. Number.
annualInterestNoannualInterest. Number.
monthlyCashFlowNomonthlyCashFlow. Number.
officialValuationNoofficialValuation. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing a concrete cost ($0.04 USDC), the transport (POST /api/v1/property-intelligence/investment-metrics), and the payment-gating behavior: an unpaid call returns x402 payment terms and does not execute. It also declares a modeling constraint ('No loan-to-value is assumed'). It does not describe output shape or error behavior, but an output schema exists for the former.

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 compact sentences: computation and its input basis first, then the modeling constraint, then price and endpoint. Every element is decision-relevant. The raw endpoint path is the least valuable line but still useful for transport/payment context.

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?

With rich annotations and an output schema, the description's remaining burden is commercial and behavioral context, which it covers: cost, payment gating, and no implicit assumptions. The one gap is that all 18 parameters are optional, so an agent cannot tell from the description what minimum input set actually produces metrics or what a degenerate call returns.

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 coverage is 100% across 18 documented, all-optional parameters, so the schema already carries the semantics. The description names six inputs (price, rent, costs, deposit, mortgage rate) and clarifies they are used as-is with no LTV inference, but says nothing about the other twelve fields (currency, rentPeriod, floorAreaSqm, etc.) or which combination is actually needed.

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 verb ('Calculate') and enumerates the concrete outputs: net yield, price per square metre, loan, and cash flow. It also bounds the input basis ('only from supplied price, rent, costs, deposit, and mortgage rate'), which separates it from lookup-style siblings. It does not explicitly distinguish itself from the sibling rent-yield-calculate, 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 Guidelines3/5

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

Usage is implied rather than stated: use it when you already have price, rent, costs, deposit and mortgage rate, and want derived metrics without external assumptions. There is no explicit 'use X instead when...' guidance against the overlapping rent-yield sibling, and no statement of what happens if required-in-practice inputs are omitted.

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