properties_surroundings_public_housingProperties around the subject flagged by the public-housing classifier.
Price: 15¢ per call.
| Name | Required | Description | Default |
|---|---|---|---|
| gnaf_id | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "properties": {
- "available": {
- "anyOf": [
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
- ],
- "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
- "title": "Available"
- },
- "data": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Public-housing classifier flags for properties around the subject.",
- "example": {
- "flagged": [
- {
- "address": "3 The Bulwark",
- "gnaf_pid": "GANSW704349559",
- "lat": -33.80311,
- "lng": 151.21899,
- "ph_chance": 3
- }
- ],
- "flagged_count": 1,
- "gnaf_pid": "GANSW704360755",
- "property_count": 128,
- "radius_m": 200
- },
- "properties": {
- "flagged": {
- "description": "The flagged properties (empty when none).",
- "items": {
- "additionalProperties": true,
- "description": "One property flagged by the public-housing classifier.",
- "properties": {
- "address": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Street address (title-cased).",
- "title": "Address"
- },
- "gnaf_pid": {
- "description": "GNAF PID of the flagged property.",
- "title": "Gnaf Pid",
- "type": "string"
- },
- "lat": {
- "description": "Latitude (EPSG:4326).",
- "title": "Lat",
- "type": "number"
- },
- "lng": {
- "description": "Longitude (EPSG:4326).",
- "title": "Lng",
- "type": "number"
- },
- "ph_chance": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Classifier confidence band (2 or 3 — every returned row is a positive prediction).",
- "title": "Ph Chance"
- }
- },
- "required": [
- "gnaf_pid",
- "lat",
- "lng"
- ],
- "title": "PublicHousingFlag",
- "type": "object"
- },
- "title": "Flagged",
- "type": "array"
- },
- "flagged_count": {
- "description": "How many of those the classifier flags as public housing.",
- "title": "Flagged Count",
- "type": "integer"
- },
- "gnaf_pid": {
- "description": "The subject property's GNAF PID.",
- "title": "Gnaf Pid",
- "type": "string"
- },
- "property_count": {
- "description": "Total properties inside the search box.",
- "title": "Property Count",
- "type": "integer"
- },
- "radius_m": {
- "description": "Radius of the search box around the subject, metres.",
- "title": "Radius M",
- "type": "integer"
- }
- },
- "required": [
- "gnaf_pid",
- "radius_m",
- "property_count",
- "flagged_count",
- "flagged"
- ],
- "title": "SurroundingPublicHousing",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "The endpoint's payload, or `null` when Microburbs has no value."
- },
- "message": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Human-readable explanation. Omitted on success.",
- "title": "Message"
- },
- "reason": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
- "title": "Reason"
- }
- },
- "title": "ApiResponse[SurroundingPublicHousing]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SurroundingPublicHousing_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds contextual scope ('around the subject' and 'public-housing classifier') and the price, but does not explain what a 'flag' means, how results are structured, or any quirks of the classifier. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise and front-loaded: the first sentence states the core function, and the second adds the price. Every word earns its place, with no filler or repetition of annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, read-only lookup with strong annotations, the core is present: what it returns (surrounding public-housing flags) and the subject identifier. However, the output is not described and no output schema exists, so an agent is left uncertain about the response shape or what 'flagged' means in practice.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain gnaf_id or its expected format. The phrase 'around the subject' vaguely implies gnaf_id identifies the property, but the agent must infer this. There is no compensation for the absent schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear resource and action: properties around the subject flagged by the public-housing classifier. The title adds the 200 m radius, which further clarifies scope. However, it does not explicitly distinguish the tool from siblings like properties_risks_public_housing or suburbs_shapes_public_housing_sa1.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No usage guidance is provided. The description does not say when to prefer this tool over related siblings, nor does it mention exclusions or prerequisites. The only non-descriptive addition is pricing, which does not help with tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.