Voxhouses (Portugal)

search_properties

Read-onlyIdempotent

Search current residential, rural and commercial real-estate listings for sale or rent in Portugal. Use this whenever the user wants to find, compare or explore properties — by location, budget, typology, property type, condition or energy rating. Returns price, price per m², typology, areas, neighbourhood, source and a citable listing URL, plus total: the exact number of listings matching the filters, which makes this tool usable to answer 'how many' questions. Listings are aggregated from portals and agency sites and refreshed continuously; each result carries the date it was last checked at the source. Sources publish uneven detail: filtering on an attribute silently excludes listings that omit it, so prefer the broadest filters that answer the question and report total as a floor, not a census.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page number. Use it with `total` to walk through a large result set.
`sort`	No	Result order. Default `recent` (most recently published first).
`limit`	No	Results per page (default 10, max 20).
`minArea`	No	Minimum floor area in m². Matches either the gross or the useful area, whichever the source published. Only matches listings that published an area.
`location`	No	Location: district, municipality, neighbourhood, town or postal-code prefix (e.g. Lisbon, Cascais, Chiado, 2750). Not a free-text keyword search — words that are not places (e.g. 'sea view') will not match.
`priceMax`	No	Maximum price, in the market currency. Note: listings advertised 'price on request' have no price and are excluded by either price bound.
`priceMin`	No	Minimum price, in the market currency.
`typology`	No	Normalised typology code (T0, T1, T2, T3…), where the number is the count of bedrooms. Used in every market, including the German and Polish ones. Matched exactly; pass an array to match several. The buckets `T0–T1` and `T4+` are also accepted.
`condition`	No	State of repair, or an array of states. Only matches listings whose source published it.
`operation`	No	buy = for sale, rent = to let. Defaults to buy; a listing is one or the other, so call twice to cover both.
`energyClass`	No	Energy certificate class. Selects the whole band the class belongs to: A+/A, B/B-, C, or D-and-below. Only matches listings that carry a certificate.
`minBathrooms`	No	Minimum number of bathrooms. Only matches listings whose source published a bathroom count.
`propertyType`	No	Property type, or an array of types. Omit to search all types. `farm` covers rural estates (quintas); `building` is a whole apartment block.

Output Schema

TableJSON Schema

Name	Required	Description
`page`	Yes
`shown`	No	Listings returned on this page.
`total`	Yes	Exact number of listings in this market matching the filters, across all pages.
`market`	Yes	ISO country code of this market.
`hasMore`	Yes	true when further pages are available.
`currency`	No
`pageSize`	No
`operation`	No	The operation actually searched (comprar = for sale, arrendar = to let).
`properties`	Yes

TDQS

A4.1/5.0

Behavior5/5

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

The description explicitly discloses non-obvious behaviors: 'filtering on an attribute silently excludes listings that omit it' and instructs to treat `total` as a floor, not a census. It also reveals data provenance and freshness cadence ('aggregated from portals and agency sites and refreshed continuously') and per-result source-check dates. These go well beyond the annotations, which only cover read-only, non-destructive, idempotent traits.

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?

Five sentences, each serving a distinct purpose: stating what the tool does, when to use it, what it returns, how data is sourced, and a critical caveat. The description is information-dense without padding, and the caveat is placed last as a practical warning. It could not be meaningfully shorter without losing value.

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?

The description covers purpose, use case, return highlights, data freshness, and a critical caveat about silent filtering. Since an output schema exists and all parameters are documented in the schema, the description does not need to enumerate returns. The main gap is not explaining how this tool relates to the sibling `search_properties_by_description`, which would help tool selection.

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?

The input schema already provides 100% coverage for all 13 parameters with individual descriptions, so the description does not need to add parameter-level detail. It references filter dimensions such as location, budget, typology, property type, condition, and energy rating, but does not add semantics beyond the schema. Baseline 3 is appropriate.

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 first sentence clearly states the verb ('search'), resource ('current residential, rural and commercial real-estate listings for sale or rent in Portugal'), and geographic scope. It does not explicitly differentiate from the close sibling `search_properties_by_description`, but the specific scope is enough to distinguish it from non-property search tools.

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 a direct when-to-use directive: 'Use this whenever the user wants to find, compare or explore properties — by location, budget, typology, property type, condition or energy rating.' It also notes the tool can answer 'how many' questions via `total`. However, it does not name alternative sibling tools or state when not to use them.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Voxhouses (Portugal) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

The two property-search tools overlap slightly, but their descriptions clearly separate structural filtering from free-text description ranking, and get_market_stats is explicitly positioned as statistical aggregation rather than listing retrieval. search_articles and search_neighbourhoods both serve editorial content, but their domains—process guidance versus area guides—are distinguishable enough.

Naming Consistency5/5

All tools use snake_case and follow a consistent search_/get_/find_ verb pattern keyed to the returned object type: search_properties, search_articles, search_neighbourhoods, get_property_detail, get_market_stats. The longer search_properties_by_description still fits the convention and is unambiguous.

Tool Count5/5

Seven tools is well-scoped for a read-only property information server: structured listing search, semantic listing search, similar-property lookup, detail retrieval, market statistics, neighbourhood guides, and editorial articles. Each tool serves a distinct user need without redundancy.

Completeness5/5

The tool surface covers the full informational workflow for Portuguese real estate: finding properties, exploring similar options, viewing full details, comparing market prices, and learning about areas and buying processes. There are no obvious dead ends for typical read-only property questions.

Resources

Need Help?