Skip to main content
Glama

BRAINIAC Property Intelligence

Prepare a due diligence report

property-intelligence_due-diligence-report
Read-onlyIdempotent

Combine the observed listing, supplied assumptions, and any OpenStreetMap place or nearby features. Planning, crime, ownership, and valuation stay unavailable. Price $0.12 USDC. POST /api/v1/property-intelligence/due-diligence-report. 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_due-diligence-report"
  }
}

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.
comparablesNocomparables, array. 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
areaNoarea. Object.
crimeNocrime. String.
listingNolisting. Object.
metricsNometrics. Object.
summaryNosummary. String.
featuresNofeatures. Object.
findingsNofindings. Array.
planningNoplanning. String.
amenitiesNoamenities. Array.
checkedAtNocheckedAt. String.
ownershipNoownership. String.
valuationNovaluation. String.
duplicatesNoduplicates. Object.
limitationsNolimitations. Array.
marketingPhrasesNomarketingPhrases. Array.
officialValuationNoofficialValuation. Boolean.

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 readOnly, idempotent, open-world and non-destructive, and the description adds genuinely new operational facts: a $0.12 USDC price, the POST endpoint, and the payment gate where an unpaid call returns x402 terms without executing. That is exactly the kind of behavior an agent cannot infer from structured fields.

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 what is combined and immediately followed by the scope limits and payment behavior. The endpoint path is arguably redundant with the tool name but still useful context for the x402 flow; there is no filler.

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 an output schema present, return values need no explanation, and the description covers composition, exclusions, cost, and payment failure mode for a tool with 19 optional parameters. The remaining gap is behavior when no inputs are supplied, which matters because nothing is required.

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 all 19 parameters are optional with typed bounds, so the schema carries the semantics. The description only gestures at the input categories ('observed listing, supplied assumptions') and adds no guidance on which fields matter, how comparables are used, or what happens with an empty payload.

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?

The description uses a specific verb ('Combine') with named inputs (observed listing, supplied assumptions, OpenStreetMap place or nearby features) and explicitly bounds the scope by declaring that planning, crime, ownership, and valuation 'stay unavailable', which separates it from siblings such as planning-search and overview.

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 makes the use case clear: an aggregate report built from a listing plus assumptions plus location features, and it tells the agent what will NOT be produced. It stops short of naming sibling tools or saying when another report tool should be chosen 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