Skip to main content
Glama

Houski Property Data

map_endpoint

Get map data: pins, clusters, or heatmaps. Billed per cluster or heatmap cell returned, or per value returned for pins. Scope it with all four bbox coordinates or a polygon: with neither, every property in every country is in scope. A heatmap needs all four bbox coordinates, and a heatmap scoped by a polygon alone is refused. Modes: cluster=true, heatmap=true. There is no cap on how many properties a request may match, so set abort_over yourself if you want a request to give up past a certain number. For maps of active inventory, add has_expand_listings_eq=true to filters so listing-less parcels don't pad results.

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": "map_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination, pins only (default: 1)
selectNoComma-separated fields to return
api_keyYesAPI key for authentication
clusterNoForce clustering (default: false)
excludeNoSource classes to leave out, comma separated, such as "inferred" or "inferred,observed". Checks the selected fields that have a source column and the heatmap field, and a heatmap of a field uses only the kept values (heatmap_values_used counts them).
filtersNoFilters array. Format: "field_operator=value", with the value as plain text and not URL encoded. Use search_api_documentation for reference.
heatmapNoEnable heatmap mode (default: false)
polygonNoPolygon coordinates "lat_lng,lat_lng,lat_lng", an alternative to bbox for pins and clusters. A heatmap needs all four bbox values and is refused with a polygon alone.
abort_overNoAbort if results exceed this count (cost protection)
bbox_ne_latNoBounding box northeast latitude
bbox_ne_lngNoBounding box northeast longitude
bbox_sw_latNoBounding box southwest latitude
bbox_sw_lngNoBounding box southwest longitude
price_quoteNoReturn the cost of this request without billing it or returning data
cluster_overNoAuto-cluster when results exceed this count
results_per_pageNoResults per page (for pins only)
heatmap_cell_limitNoMax heatmap cells (default: 1000, max: 10000)
heatmap_aggregation_typeNoHeatmap aggregation: "mean", "median", or "sum"
heatmap_aggregation_fieldNoField for heatmap intensity (e.g., "estimate_list_price"). Without this, uses density.
heatmap_aggregation_invert_intensityNoInvert intensity (true = lower values show higher intensity, good for affordability)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 well: it discloses the billing model (per cluster, per heatmap cell, per pin value), that there is no result cap, the abort_over escape hatch, and the refusal case for polygon-only heatmaps. It leaves the response shape unexplained (no output schema exists), so an agent still doesn't know what a pin or cluster record contains.

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?

Output modes are front-loaded in the first clause and billing immediately after, so a skimming agent gets the essentials first. The prose is dense and a few sentences bundle two ideas (e.g. bbox-plus-refusal), but nearly every clause carries operational information.

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 20-parameter, no-annotation, no-output-schema tool, the description covers the decisions that matter most: mode selection, geographic scoping, cost exposure, and one filter caveat. It is not exhaustive over pagination, select/exclude, and heatmap aggregation options, but those are documented in the schema, so the remaining gap is mainly return-value expectations.

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 3 is the baseline. The description does add cross-parameter meaning the schema cannot, notably that a heatmap requires all four bbox values and is refused with a polygon alone, and that abort_over is the caller's own protection against uncapped matches; the remaining ~15 parameters are left entirely to 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?

The opening sentence names a specific verb and resource ("Get map data") and immediately enumerates the three output shapes: pins, clusters, heatmaps. It is clear what the tool produces, though it never contrasts itself with nearby siblings like search_endpoint or properties_endpoint, which also return property data.

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?

The description gives concrete conditions for each mode (cluster=true, heatmap=true), states how to scope with bbox versus polygon and what happens with neither, and adds a useful conditional for active-inventory maps via has_expand_listings_eq. It stops short of saying when a caller should reach for this tool instead of the sibling search/properties tools.

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