Skip to main content
Glama

Houski Property Data

geocoding_endpoint

Find properties near coordinates (reverse geocoding). Billed per value returned. Required: latitude, longitude. Optional: radius (km), shape (circle/square). This endpoint has no country, province, city, community or address parameters. To narrow by place, put filters such as country_abbreviation_eq=CA or city_eq=Calgary in filters, spelled exactly as location_endpoint returns them, letter case included. For active or marketable properties, add has_expand_listings_eq=true to filters, which is far cheaper than expanding listings just to filter on their presence.

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "geocoding_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination
shapeNoSearch shape: "circle" (default) or "square"
expandNoComma-separated. Values: "listings", "listings_rent", "permits", "assessments". Each attached record is a flat charge. To filter to properties that HAVE a set, use the has_expand_* boolean filters instead.
radiusNoSearch radius in kilometers
selectNoComma-separated fields to return, or "all"
api_keyYesAPI key for authentication
excludeNoSource classes to leave out, comma separated, such as "inferred" or "inferred,observed". Checks the selected fields that have a source column, keeps a property when one of them keeps its value, and empties the rest.
filtersNoFilters array. Format: "field_operator=value", with the value as plain text and not URL encoded. Use search_api_documentation for reference.
latitudeYesCenter latitude (e.g., 51.0447)
longitudeYesCenter longitude (e.g., -114.0719)
price_quoteNoReturn the cost of this request without billing it or returning data
results_per_pageNoResults per page
filter_expand_matchNo"any" or "all". Use only when filtering on values inside expanded records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral trait: billing is per value returned, and it warns that expanding listings just to test presence is expensive compared with a boolean filter. It does not cover rate limits, error behavior on malformed filters, pagination defaults, or authentication expectations beyond the api_key parameter.

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 tight sentences, front-loaded with the operation and billing model, then required/optional parameters, then the place-filter workaround, then the cost optimization. No filler and nothing repeated from the schema verbatim without added meaning.

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?

For a 13-parameter, no-annotation, no-output-schema tool, the description covers the essential decision points: what it does, what it costs, what it cannot do, and how to work around the missing place parameters. Gaps remain around pagination/result-size expectations and what the returned property records look like, which matter for an agent planning a multi-page or costly call.

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%, so the baseline is 3, but the description adds genuine meaning beyond the schema: it restates the required pair, the km unit for radius, the circle/square shape choices, and — most importantly — the exact filter string syntax with worked examples and the letter-case sensitivity rule. It leaves `select`, `exclude`, `page`, and `filter_expand_match` to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ("Find properties near coordinates") and names the mechanism (reverse geocoding), so the agent immediately knows this is a spatial lookup rather than a text/place search. It also carves itself away from the location-style sibling by explicitly declaring which place-name parameters do NOT exist here.

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?

Gives concrete routing guidance: place-based narrowing must go through `filters` with values spelled exactly as `location_endpoint` returns them, and it names `has_expand_listings_eq=true` as the cheap alternative to `expand`. What it lacks is an explicit statement of when to prefer this tool over `search_endpoint`/`properties_endpoint` for non-spatial queries.

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