SiteCheck Jobs & Property

Zoocasa homes for sale in a city: MLS number, address

realestate_zoocasa

Read-only

Zoocasa (Canada) homes for sale in a city: MLS number, address, neighbourhood, price (CAD), property type, bedrooms, bathrooms, maintenance fee, garage, brokerage, feature tags, listed time and link, about 27 per page (page 1 to 20), plus the total number of listings. From zoocasa.com's public city pages via a residential proxy. Related tools on this server, for a different need: realestate_estately when you need US homes for sale from Estately for a city: per listing; realestate_hemnet when you need Hemnet homes for sale in an area: address, housing form. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": {
      "city": "<city>",
      "province": "<province>"
    },
    "name": "realestate_zoocasa"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City name, e.g. toronto, vancouver, calgary
`page`	No	Results page 1 to 20 (default 1)
`province`	Yes	Two-letter province code, e.g. on, bc, ab

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover readOnlyHint and openWorldHint; the description adds substantial behavior beyond them: the data comes from public city pages via a residential proxy, ~27 records per page capped at pages 1-20, a total-count field is included, and the call costs $0.002 USDC via x402 with failed calls not charged. The pricing/failure-charging detail is exactly the kind of operational fact an agent needs before invoking.

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?

Content is front-loaded: purpose and field coverage first, then siblings, then pricing. The field enumeration is long but each item is information the caller uses; the only slight overhead is the awkward 'Related tools on this server, for a different need' framing.

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?

An output schema exists, yet the description still summarizes the payload and pagination, and it covers source, cost and sibling routing. For a three-parameter, read-only scraper tool nothing needed to call it correctly is missing.

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 description coverage is 100%, so city, province and page are already documented with examples, setting the baseline at 3. The description reinforces the page constraint ('about 27 per page (page 1 to 20)') but adds no new syntax or format meaning for the parameters.

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?

The description opens with a specific verb, resource and geography: 'Zoocasa (Canada) homes for sale in a city', then enumerates the exact fields returned (MLS number, price in CAD, bedrooms, brokerage, etc.). It also names the two sibling tools it differs from (realestate_estately for US, realestate_hemnet for Sweden), so an agent can disambiguate without opening a schema.

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?

It explicitly routes the agent: use this for Canadian city listings, use realestate_estately for US city listings, use realestate_hemnet for Swedish area listings. That is an explicit alternative-plus-condition statement rather than implied usage.

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

All SiteCheck Jobs & Property tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?