Skip to main content
Glama

Houski Property Data

search_endpoint

Find property_id using fuzzy address matching. Billed per value returned. Handles typos, abbreviations, partial addresses. Pass country_abbreviation to keep every match in one country. Use returned property_id with other endpoints for detailed data.

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>",
      "query": "<query>"
    },
    "name": "search_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesAddress query. Handles partial addresses, building names, typos. Include city for better accuracy.
selectNoComma-separated fields to return
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 match when one of them keeps its value, and empties the rest.
max_resultsNoMax results (default: 10, max: 25)
price_quoteNoReturn the cost of this request without billing it or returning data
country_abbreviationNoOnly return matches from one country, by its country_abbreviation as location_endpoint returns it (for example "GB"). Default: every country. A query that names a province, a state, or a postal code already ranks its own country first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses per-value billing and fuzzy matching for typos, abbreviations, and partial addresses, but omits authentication requirements, rate limits, error behavior, and the full response shape.

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?

Five short sentences, front-loaded with purpose, billing, matching tolerance, country filtering, and downstream use. No wasted wording.

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?

No output schema exists, and the description names only the returned property_id rather than the full result shape, ranking, or what a billed "value" includes. For a seven-parameter search endpoint, it should describe the response more fully.

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. The description adds meaning beyond the schema for country_abbreviation (constrains matches to one country, defaults to every country) and reinforces query tolerance and billing implications.

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 specific verb and resource: "Find property_id using fuzzy address matching." The purpose is clear and distinct, though it does not explicitly contrast with geocoding_endpoint or location_endpoint.

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 useful downstream guidance: "Use returned property_id with other endpoints for detailed data," and explains when to pass country_abbreviation. However, it does not say when to use this tool instead of siblings such as geocoding_endpoint or location_endpoint.

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