SiteCheck Jobs & Property

Houzz home-improvement professionals of one category near

realestate_houzz

Read-only

Houzz home-improvement professionals of one category near a US city (e.g. general-contractors, interior-designers-and-decorators, home-builders, painters): name, categories, rating (0-5), review count, projects on Houzz, cost estimate, address, phone, distance, coordinates, sponsored flag and profile URL; 15 organic results per page (plus Houzz sponsored ones, flagged) in Houzz order, and the total count. Related tools on this server, for a different need: realestate_healthgrades when you need Doctors near a US city from Healthgrades' specialty; realestate_nobroker when you need NoBroker India owner-listed homes for rent or resale near. 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": {
      "category": "<category>",
      "city": "<city>",
      "state": "<state>"
    },
    "name": "realestate_houzz"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	US city, e.g. Austin (required)
`page`	No	Page number from 1 (default 1)
`state`	Yes	2-letter state code, e.g. TX (required)
`category`	Yes	Houzz category slug, e.g. general-contractors, interior-designers-and-decorators, home-builders, painters (required)

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 declare readOnlyHint and openWorldHint; the description adds substantially more: the exact result mix (15 organic per page plus flagged Houzz sponsored entries), the ordering ('Houzz order'), the total count, and the full field set returned. It also discloses the commercial behavior an agent must know before calling — $0.002 USDC per successful call via x402 on Base/Solana/Arc, with failed calls not charged.

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?

Purpose and scope are front-loaded, and the related-tools and pricing sentences each earn their place. The core sentence is heavily packed with a long field enumeration, which makes it dense to scan, but no sentence is redundant for a tool with this much surface area.

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 four-parameter, open-world read tool with an output schema, everything an agent needs is present: geographic and category scoping, pagination size, result ordering, sponsored-result flagging, and the payment model. Return-value detail is partly redundant given the output schema, but nothing is missing.

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 to the otherwise bare 'page' parameter by stating there are 15 organic results per page plus sponsored entries in Houzz order. It does not help with discovering valid category slugs beyond four examples, which is the one remaining parameter-level ambiguity.

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-plus-resource statement: Houzz home-improvement professionals of one category near a US city, and enumerates concrete category examples (general-contractors, interior-designers-and-decorators). It also immediately separates this tool from realestate_healthgrades (doctors) and realestate_nobroker (India rentals), so an agent can distinguish it from the large sibling list 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit routing to two named alternatives with the condition that selects each ('when you need Doctors near a US city', 'when you need NoBroker India owner-listed homes'). What it lacks is an explicit exclusion for this tool itself, such as non-US cities or unsupported category slugs, leaving the agent to infer the boundary from 'near a US city'.

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?