A BC lot's public-record report
parcel_reportOne lot's report by PID: for each section a status (flag = look into, clear = nothing to flag, info = for reference, gap = not covered here, error = not available yet) and a one-line answer; for the sections named, also the facts behind it, notes, and sources with licences. Sections: zoning, buildable, sun, alr, soil, flood, fire, evac, seismic, landslides, radon, fcsi, access, water, lake, minerals, habitat, nextdoor, noise, wells, septic, services, internet, climate, svt, tax, crime (the lake section only beside a sampled lake). Zoning rules are our dated summary of the bylaw. A lot nobody has looked up yet takes 10 to 20 seconds to build. No scores, valuations or owner names.
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": {
"pid": "<pid>"
},
"name": "parcel_report"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pid | Yes | The lot's 9-digit PID, with or without dashes (find_parcel gives it). | |
| full | No | Every section in full: about 100 KB, sent twice in the reply (as structured content and as text). Name sections instead to keep it small. | |
| sections | No | Sections to give in full (facts, notes, sources); the others come as status and headline only. |