Skip to main content
Glama

Houski Property Data

location_endpoint

Get the places Houski holds property data for, as a hierarchy of countries, provinces (or states or regions), cities and communities, with links and slugs. Billed per location returned, a small fraction of a cent each. This is the source of every country_abbreviation, province_abbreviation, city and community the other tools take. There is no paging and every matching location comes back, so scope every call: resolution=country and resolution=province are small, while resolution=city or community with no country_abbreviation and province_abbreviation returns every city of every country in one very large response. Naming a level requires naming its parents, and the endpoint returns a 400 saying so if you skip one. filters keeps only the places where at least one property matches, which is the cheapest way to check coverage: resolution=country with filters=["parcel_number_regex=."] lists only the countries that hold parcel numbers.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name. Requires country_abbreviation and province_abbreviation, and the endpoint returns a 400 if either is missing.
flatNoReturn flat format instead of nested (default: false). Flat is roughly four times larger, because each row repeats the whole country and province block instead of nesting under it, and carries a null key for every level below the resolution. Prefer nested unless you specifically want one row per location.
api_keyYesAPI key for authentication
filtersNoFilters that keep only the locations holding at least one matching property, in the "field_operator=value" form. "<field>_regex=." keeps the places where some property has a value for that field, which is how to check a field's coverage by country or region.
communityNoCommunity/neighborhood name. Requires country_abbreviation, province_abbreviation and city, and the endpoint returns a 400 if any is missing.
resolutionNoDepth: "country", "province", "city", or "community" (default). This is the main size lever. With no country_abbreviation and province_abbreviation, stay on "country" or "province".
price_quoteNoReturn the cost of this request without billing it or returning data
country_abbreviationNoCountry abbreviation (for example "CA"). Pass it with province_abbreviation on anything finer than resolution=province, or the response covers the whole country.
province_abbreviationNoProvince, state or region abbreviation (for example "AB"). Requires country_abbreviation. The two together keep a resolution=city call to one province instead of every city of the country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/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 so well: it discloses per-location billing, the absence of paging, the 400 behavior when a parent level is skipped, and that flat format is roughly four times larger with null keys for sub-levels. It does not describe the concrete response envelope beyond hierarchy plus links and slugs, which keeps it short of a 5.

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?

Front-loads what the tool returns and its billing model, then moves to scoping rules and the filters trick in descending order of importance. Sentences are dense but every one carries a distinct constraint or cost implication, with no filler.

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 9-parameter geography tool with no output schema, the description covers return shape, cost, error behavior, size hazards and parameter interdependencies. An agent can call it correctly and predict the response size and bill from the description alone.

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 real meaning beyond it: filters is explained as a coverage probe with the parcel_number_regex example, and resolution is framed as the main size lever with parent-naming prerequisites. The flat-format size comparison also adds cost intuition the schema only briefly mentions.

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 — retrieves the hierarchy of countries, provinces, cities and communities where Houski holds property data — and adds scope detail (links, slugs, billing per location). It also positions itself relative to siblings by declaring itself the source of every country_abbreviation, province_abbreviation, city and community the other tools consume.

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?

Gives explicit operational guidance: scope every call because there is no paging, stay on resolution=country or province when no abbreviations are supplied, and use filters as the cheapest coverage check. It also warns which call shapes produce a very large response, which is exactly the when-not guidance an agent needs.

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