Skip to main content
Glama

Houski Property Data

properties_endpoint

Retrieve property data (hundreds of fields) with filtering, sorting, and expansion. Billed per value returned: each selected field's price for each home that has a value for it, so a field with no value for a home is not billed. Always set select= to limit fields. For comparables, 'good' properties, or active inventory, add has_expand_listings_eq=true to filters: a fast indexed boolean filter that excludes the long tail of listing-less parcels (use has_expand_listings_rent_eq=true for rentals). Use expand=listings,permits,assessments only when you actually need the related records, not just to filter on their existence (has_expand_permits_eq=true and has_expand_assessments_eq=true cover that). Take place names and abbreviations from location_endpoint. When select names a field with a source column, pass exclude=inferred unless the user wants inferred values too or the call looks up one named property. Set price_quote=true first when the row count is unknown. See search_api_documentation for full filter syntax.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "api_key": "<api_key>"
    },
    "name": "properties_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name as location_endpoint returns it (for example "Calgary"). Letter case, accents and punctuation do not matter. Requires country_abbreviation and province_abbreviation, and the request is refused with a 400 error if either is missing.
pageNoPage number for pagination (default: 1)
expandNoComma-separated. Values: "listings", "listings_rent", "permits", "assessments". Each attached record is a flat charge, so only include when you need the related records themselves. To filter to properties that HAVE a set, prefer the indexed boolean filters passed via `filters` (has_expand_listings_eq=true, has_expand_listings_rent_eq=true, has_expand_permits_eq=true, has_expand_assessments_eq=true) over expanding with `filter_expand_match=all`. They are far faster and cheaper.
selectNoComma-separated fields to return, or "all". Use field_list to discover fields.
addressNoAddress for a single property lookup. Letter case and punctuation do not matter, but abbreviations are not rewritten, so write road types in full as the address field does ("Place", not "Pl"). Requires country_abbreviation, province_abbreviation and city. For fuzzy, abbreviated or partial addresses use search_endpoint instead.
api_keyYesAPI key for authentication
excludeNoSource classes to leave out, comma separated: "inferred" leaves out every value Houski worked out, and "inferred,observed" keeps only values from a linked public record. Checks the selected fields that have a source column (field_detail names it), keeps a property when one of them keeps its value, and empties the rest. search_api_documentation page filter lists every class.
filtersNoFilters array. Format: "field_operator=value", with the value as plain text and not URL encoded. Operators: _eq, _neq, _gte, _lte, _gt, _lt, _in, _regex, _nregex (rows that do not match the regex). Text values compare exactly, letter case included (property_type_eq=House). To narrow to a place, use the country_abbreviation, province_abbreviation, city, community and address arguments, which ignore letter case, rather than filters such as city_eq. Use search_api_documentation for full reference.
polygonNoPolygon coordinates "lat_lng,lat_lng,lat_lng", latitude and longitude joined by an underscore. Maximum 100 points, simplify a shape that has more.
sort_byNoSort field. Format: "field_sort=asc" or "field_sort=desc"
communityNoCommunity/neighborhood name. Letter case, accents and punctuation do not matter. Requires country_abbreviation, province_abbreviation and city, and the request is refused with a 400 error if any is missing.
bbox_ne_latNoBounding box northeast latitude. All four bbox values are required together.
bbox_ne_lngNoBounding box northeast longitude. All four bbox values are required together.
bbox_sw_latNoBounding box southwest latitude. All four bbox values are required together.
bbox_sw_lngNoBounding box southwest longitude. All four bbox values are required together.
price_quoteNoReturn the cost of this request without billing it or returning data
community_inNoSeveral community names, comma separated. This is a plain filter on the community name, so it compares each name exactly, letter case included, and spelled as location_endpoint returns it. It needs no other location parameter, but without city it matches communities with those names in every city.
results_per_pageNoResults per page (default: 6, max: 1000)
filter_expand_matchNo"any" or "all". Use this only when filtering on values inside expanded records (for example expand_permit_content_regex). To filter on mere presence of a set, use the has_expand_* boolean filters in `filters` instead.
country_abbreviationNoCountry abbreviation as location_endpoint returns it (for example "CA", "US", "GB" or "KR"). Any letter case is accepted.
province_abbreviationNoProvince, state or region abbreviation as location_endpoint returns it (for example "AB" in Canada). Any letter case is accepted. Requires country_abbreviation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so unusually well: it explains the per-value billing model, including that a field with no value for a home is not billed, and that each expanded record is a flat charge. It also discloses the cost/fastness tradeoff between indexed boolean filters and expansion, which is behavior an agent cannot infer from the schema.

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?

Front-loaded with purpose and the billing constraint before branching into per-task guidance; nearly every clause carries actionable information. It is dense and runs long as a single block, so scanning for a specific rule takes effort, but little is genuinely redundant.

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

Completeness5/5

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

For a 21-parameter tool with no output schema and no annotations, the description covers the decisions that matter: field limiting, expansion cost, presence filters, inferred-value exclusion, quote-before-query, and pointers to the documentation and location tools. No critical gap remains for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so a 3 would be the floor, but the description adds real decision-level meaning: when select names a source column pass exclude=inferred unless inferred values are wanted or it is a single named-property lookup, and why has_expand_listings_eq beats expanding with filter_expand_match=all. These are usage rules the parameter descriptions alone do not fully encode.

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?

Opens with a specific verb and resource ('Retrieve property data (hundreds of fields)') and immediately scopes it with filtering, sorting and expansion. It also distinguishes itself from search_endpoint and location_endpoint by pointing to them for fuzzy addresses and place names, so an agent can route correctly without opening another schema.

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

Usage Guidelines5/5

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

Explicit when-to guidance across several decisions: always set select=, add has_expand_listings_eq=true for comparables/good properties/active inventory (with the rentals variant), only use expand= when the related records themselves are needed, and prefer the has_expand_* booleans over filter_expand_match=all. It also names the alternatives (location_endpoint, search_api_documentation) and states when to run price_quote=true first.

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