Skip to main content
Glama

BRAINIAC Property Intelligence

Extract a listing

property-intelligence_listing-extract
Read-onlyIdempotent

Read price, rent, address, and room counts from caller-supplied listing text or one public listing page. Missing figures stay blank. Price $0.05 USDC. POST /api/v1/property-intelligence/listing-extract. 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_listing-extract"
  }
}

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.
fieldsNofields. Array.
findingsNofindings. Array.
checkedAtNocheckedAt. String.
limitationsNolimitations. Array.
officialValuationNoofficialValuation. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely new behavior: the $0.05 USDC fee, the POST endpoint, and the fact that an unpaid call returns x402 payment terms instead of executing. That payment-gate behavior is exactly the kind of non-obvious trait an agent needs. It does not describe output shape, but an output schema exists.

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 core action and followed by constraint, cost, and failure mode. Little waste; the raw endpoint path is arguably the least useful line for an agent but is compact.

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?

Covers cost, transport, and the payment failure path, and the output schema handles return values. For an 18-parameter tool, though, it omits the crucial interaction between the free-text/page inputs and the many structured numeric fields, and whether at least one of text/url must be supplied.

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%, so baseline 3 applies, and the schema descriptions are purely mechanical (type plus range) so they add little meaning. The description names only four of the eighteen fields and never explains how the scalar fields (deposit, mortgageRate, floorAreaSqm, currency, latitude/longitude) relate to text/url — as overrides, fallbacks, or hints — which is the main semantic gap.

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 concrete verb (read/extract) and the exact fields recovered (price, rent, address, room counts), plus the two supported input sources. The scope is unambiguous and clearly distinct from siblings such as listing-duplicate-detect or details-normalize, 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?

Gives usable context: supply listing text or one public listing page, and missing figures stay blank. However it never states when to prefer this over related tools (description-analyze, details-normalize) and does not say whether text or url is actually required given that all 18 parameters are marked optional.

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