BhumiBoss Hyderabad Homes

View saved version →

---
name: research-hyderabad-homes
description: Find, evaluate, and compare Hyderabad gated apartment or villa communities using BhumiBoss MCP search, project, and comparison tools, plus public pages. Use for project shortlists, buyer questions, side-by-side comparisons, density and amenity analysis, floorplan research, builder track record, and property due diligence in Hyderabad.
---

# Research Hyderabad homes with BhumiBoss

Use the BhumiBoss MCP tools `search_projects`, `get_project`, and `compare_projects` to resolve names, fetch details, and compare projects. The tools are read-only and return public, buyer-facing data from BhumiBoss's APIs. Fetch current data for each answer; do not rely on a remembered inventory, a stale snippet, or an earlier answer. Use public pages at `https://www.bhumiboss.com/` for buyer-facing links, floorplans, additional context, and fallback. No logged-in session or credentials are supplied by this plugin.

## Find projects

1. Interpret the buyer's constraints: apartment/villa, location, budget, BHK, minimum area, handover/ready date, commute, priorities, and deal breakers. Ask only for a missing constraint that materially affects the result; otherwise state a sensible assumption and start.
2. For a named project, call `search_projects` with `{ "terms": "<name>", "limit": 10 }` (limit 1–20). Inspect `suggestions` for `projectName`, `developerName`, `alias`, `location`, `uuid`, and `projectType`. Match name or alias while checking developer, location, and phase; show ambiguous matches instead of guessing. This is term lookup, not a budget or inventory search. An empty array means no suggestion for that term, not that the project does not exist.
3. For each matched UUID, call `get_project` with `{ "uuid": "<actual suggestion UUID>" }`. Check that the returned `project.uuid` and identity match the suggestion. The normalized result includes `sourceUrl`, `location`, `scale`, `completion`, `regulatory`, `amenities`, `floorplans`, `prices`, `developerHistory`, `reviewPreview`, and `warnings`. Numeric fields specify units in their names: `projectAreaAcres`, `homesPerAcre`, `minSizeSqft`, `totalAreaSqft`, `sqftPerHome`, and `observedProjectInrPerSqft` are already converted; do not convert them again. Read [project-api.md](references/project-api.md) when checking the underlying raw response, missing fields, or source-specific cautions.
4. For 2–5 distinct verified project UUIDs, call `compare_projects` with `{ "uuids": ["<uuid1>", "<uuid2>"] }`. Use its per-project summaries and `metrics` for matching-unit comparisons, then inspect each project's dates, warnings, and missing values. If the comparison omits relevant detail, use `get_project` for those projects. The comparison gives numeric spreads and does not select an overall winner.
5. Open each `project.sourceUrl` or `https://www.bhumiboss.com/project/<uuid>` for buyer-facing links, identity cross-check, missing fields, and floorplan links. If an MCP tool is unavailable or returns unusable data, try the public `GET /api/suggest/v2?terms=<URL-encoded name>` and `GET /api/project/<uuid>` APIs with an HTTP-capable tool and interpret the raw response using [project-api.md](references/project-api.md). If those are also unavailable, search for `site:bhumiboss.com/project/ <project name> Hyderabad` and say which source was available. For broader discovery, search relevant `site:bhumiboss.com/list/hyderabad/` location, builder, budget, or type pages; term lookup is not a complete inventory. Do not describe tool or API access failure as “no matching projects.”
   Collect only evidenced fields relevant to the question: builder, location, unit types and sizes, homes, site acreage, density, floors/towers, proposed handover, amenities area, amenities, notable features, builder history, and published prices. Preserve each field's source date and unit labels. `modifiedAt` does not make every nested price or inventory field current. If the API and page disagree, show both with their labels and dates; do not quietly choose one.
   For tower, floor, unit-area, or booked-count questions, read the raw `GET /api/project/<uuid>` response because the current `get_project` summary may omit `buildingDetails`. Check both root `buildingDetails` and `fileDetails.buildingDetails`, then follow the building and floor interpretation in [project-api.md](references/project-api.md). State when floor-level records are unavailable from the accessible source.
6. For a named group, an existing comparison at `https://www.bhumiboss.com/compare/<comma-separated-project-UUIDs>` may provide a reader-facing link. Verify that the page loads and the project names match before relying on or linking it.

## Compare with buyer-focused calculations

- Present compact side-by-side tables with exact values and units, followed by the meaningful strengths, weaknesses, and who each project fits. Prefer numeric differences: absolute and percentage changes, with the denominator stated when it matters. If the user asks for one narrow category, stay within that scope.
- `get_project` already computes `scale.homesPerAcre` and `amenities.sqftPerHome`. Check that homes and acreage use the same project phase or land parcel. Recalculate only if verifying a discrepancy or using raw API fields: 1 acre = 4,046.8564224 m² and 1 m² = 10.7639104167 sq ft. Amenities sq ft per home measures allocation, not actual usable access or quality.
- Keep super built-up, built-up, carpet, and balcony areas distinct. Never equate a floorplan's advertised square feet with carpet area unless the page explicitly does so. Compare the same BHK and closely matched sizes when judging layouts.
- A building's `floors[]` rows summarize apartments for a floor and apartment type. Divide `saleableArea` (m²) by `numberOfApartments` to derive the average saleable area per apartment in that row; convert to sq ft only after division. `numberOfBookedApartments` is a recorded booked count, not proof of completed sales or current availability. See [project-api.md](references/project-api.md) for grouping and validation.
- Treat blank cells as “not published,” not zero. Flag obvious inconsistencies, implausible density, mismatched phases, or conflicting project and comparison pages; do not quietly rank on them.
- Prioritize the buyer's criteria and make tradeoffs explicit. Avoid a universal best-project score or recommendations based solely on builder marketing. For a shortlist, indicate why each option was included and the strongest open question.

## Additional useful buyer research

- Examine BhumiBoss floorplans for configuration and dimensions when visible. For nearby schools, hospitals, commute, AQI, metro, or lake/FTL concerns, separate BhumiBoss's published context from external evidence; verify time-sensitive or regulatory claims with current primary sources when possible.
- Distinguish proposed completion from possession or occupancy approval. Treat listing prices, inventory, incentives, builder litigation labels, and construction progress as time-sensitive claims. Quote the source and its as-of date; recommend direct confirmation for a transaction.
- When calculating a purchase budget, label base price versus other charges, tax, registration, parking, maintenance, and financing. Do not invent a live quote, negotiable discount, or available unit.
- If information is behind BhumiBoss sign-in or a subscription, do not use a possibly exposed API field to bypass that access boundary. `get_project` provides `reviewPreview` and omits the full `review`; when using a raw API response, use only the preview and public content unless access to the full review is clearly authorized. Never imply access to insider pricing or private user data.

## Answer format

Lead with the answer or shortlist. For comparisons, use a concise table and a few decision-relevant observations. Link each project name to its specific BhumiBoss page; include a comparison link when used. Label “checked on” with the current date for live research, and distinguish the page's own last-updated date from the check date. Identify missing data and one or two next checks that could change the decision. Do not repeat long passages from the site. If BhumiBoss cannot substantiate an answer, say so and supplement with clearly labeled, cited sources instead of inventing figures.

Referenced files: 1 — file references are metadata, not package contents.