Skip to main content
Glama

BRAINIAC Property Intelligence

Normalize listing details

property-intelligence_details-normalize
Read-onlyIdempotent

Return one listing record from supplied fields or printed text. A supplied value is kept when it conflicts with the printed value. Price $0.03 USDC. POST /api/v1/property-intelligence/details-normalize. 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_details-normalize"
  }
}

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
urlNourl. String.
rentNorent. Number.
priceNoprice. Number.
titleNotitle. String.
fieldsNofields. Array.
addressNoaddress. String.
bedroomsNobedrooms. Number.
currencyNocurrency. String.
findingsNofindings. Array.
latitudeNolatitude. Null.
bathroomsNobathrooms. Number.
checkedAtNocheckedAt. String.
longitudeNolongitude. Null.
rentPeriodNorentPeriod. String.
limitationsNolimitations. Array.
floorAreaSqmNofloorAreaSqm. Number.
propertyTypeNopropertyType. String.
officialValuationNoofficialValuation. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, and the description adds substantive behavior beyond them: precedence rules on conflicting values, a concrete cost of $0.03 USDC, the HTTP endpoint, and the payment gate that returns x402 terms without executing on an unpaid call. That payment-gate disclosure is exactly the kind of operational detail an agent needs 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the operation and merge rule, then cost, endpoint, and payment failure mode. Nothing is padded and no sentence merely restates the tool name.

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 merge semantics, cost, and the unpaid-call path. The only minor gap is that all 18 parameters are optional yet the description never says what a call with no fields or text produces.

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% and all 18 fields are individually documented, so the schema carries the field-level burden. The description still adds real semantic value by explaining how the free-text parameter interacts with the structured fields and which side wins on conflict — information absent from the schema.

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 and resource: return one normalized listing record built from supplied fields or from printed text. The merge rule ('a supplied value is kept when it conflicts with the printed value') distinguishes it from a pure extraction sibling such as listing-extract, though no sibling is named explicitly.

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 only implied: the agent can infer it should call this when it already has some fields plus optional free text and wants a single merged record. There is no explicit when-to-use versus when-not-to-use guidance and no named alternative (e.g., listing-extract for text-only input).

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