SiteCheck Jobs & Property

NoBroker India owner-listed homes for rent or resale near

realestate_nobroker

Read-only

NoBroker India owner-listed homes for rent or resale near a point in 10 cities (Bangalore, Mumbai, Pune, Chennai, Hyderabad, Delhi, Gurgaon, Noida, Ghaziabad, Faridabad): ID, title, BHK, rent, deposit and maintenance or sale price, size, bathrooms, floor, furnishing, society, locality, coordinates, distance, dates and URL; 26 per page. Owner names are not returned. Related tools on this server, for a different need: realestate_seloger when you need SeLoger homes for sale or rent in a town: listing id; realestate_zoopla when you need Zoopla homes for sale or to rent in an area: headline. 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>"
    },
    "name": "realestate_nobroker"
  }
}

Input Schema

Name	Required	Description
`bhk`	No	Optional filter on the result page: 1-9 (BHK) or rk
`lat`	No	Optional latitude of the area to search around (default: city centre)
`lon`	No	Optional longitude (give with lat)
`city`	Yes	Required: bangalore, mumbai, pune, chennai, hyderabad, delhi, gurgaon, noida, ghaziabad, faridabad
`deal`	No	rent (default) or buy (resale)
`page`	No	Page number from 1 (default 1)

Output Schema

Name	Required	Description	Default
`lat`	No
`lon`	No
`city`	No
`deal`	No
`page`	No
`count`	No
`total`	No
`source`	No
`listings`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses page size ('26 per page'), a privacy constraint ('Owner names are not returned'), and a metered cost model ('$0.002 in USDC per successful call, paid with x402... failed calls are not charged'). The failed-call billing rule is exactly the kind of behavioral detail an agent needs before retrying.

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 is front-loaded and there is no filler, but the body is a single semicolon-chained run-on that mixes returned fields, pagination, privacy, sibling routing and billing. It is dense rather than wasteful, yet the field enumeration is bulky prose that is hard to scan.

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?

Pricing, pagination, privacy and alternative tools are all covered, which is thorough for a paid open-world scraper. The one redundancy is the long list of returned fields, which an output schema already supplies, so that space is spent twice.

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 coverage is 100%, so city, bhk, deal, page, lat and lon are already documented with defaults and value lists. The description adds only indirect hints ('near a point' for lat/lon, '26 per page' for page) and largely restates the city list already in the schema.

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 resource and scope: 'NoBroker India owner-listed homes for rent or resale near a point in 10 cities', then names the exact cities. An agent immediately knows this is an India owner-listed property search with point-radius support, distinguishable from the Zillow/Rightmove-style siblings.

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?

Explicitly routes to alternatives: 'realestate_seloger when you need SeLoger homes for sale or rent in a town' and 'realestate_zoopla when you need Zoopla homes for sale or to rent in an area'. The when-to-use conditions are stated, but the closer India competitors (realestate_magicbricks_india, realestate_squareyards_india) are never mentioned, so a same-country choice is left unresolved.

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?