suburbs_development_building_controlsHeight-of-building and floor-space-ratio control polygons with band summaries.
| Name | Required | Description | Default |
|---|---|---|---|
| suburb_name | 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": "Height-of-building + floor-space-ratio planning controls.\n\nEither block can be null — many LGAs map HOB but not FSR (or vice\nversa). A 404 means neither layer exists for the suburb.",
- "example": {
- "area_level": "suburb",
- "area_name": "Belmont North",
- "hob": {
- "geojson": {
- "features": [
- {
- "geometry": {
- "coordinates": [
- [
- [
- 151.668,
- -33.017
- ],
- [
- 151.672,
- -33.017
- ],
- [
- 151.672,
- -33.02
- ],
- [
- 151.668,
- -33.017
- ]
- ]
- ],
- "type": "Polygon"
- },
- "properties": {
- "band": "≤ 8.5m",
- "color": "#fef9c3",
- "height_m": 8.5,
- "units": "m"
- },
- "type": "Feature"
- }
- ],
- "type": "FeatureCollection"
- },
- "legend": [
- {
- "color": "#fef9c3",
- "label": "≤ 8.5m",
- "pct": 84.2
- },
- {
- "color": "#fbbf24",
- "label": "8.5–12m",
- "pct": 15.8
- }
- ],
- "most_common_height_m": 8.5,
- "pct_most_common": 71,
- "zones_mapped": 17
- }
- },
- "properties": {
- "area_level": {
- "description": "Always 'suburb'.",
- "title": "Area Level",
- "type": "string"
- },
- "area_name": {
- "description": "Suburb (SAL) name.",
- "title": "Area Name",
- "type": "string"
- },
- "fsr": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Floor-space-ratio controls summary + polygons.",
- "properties": {
- "breakdown": {
- "description": "Area share per FSR band.",
- "items": {
- "description": "One legend band with its share of the mapped area.",
- "properties": {
- "color": {
- "description": "Hex colour for map styling.",
- "title": "Color",
- "type": "string"
- },
- "label": {
- "description": "Band label (e.g. '8.5–12m', '≤ 0.5:1').",
- "title": "Label",
- "type": "string"
- },
- "pct": {
- "description": "Share of mapped area in this band (%).",
- "title": "Pct",
- "type": "number"
- }
- },
- "required": [
- "label",
- "color",
- "pct"
- ],
- "title": "BandShare",
- "type": "object"
- },
- "title": "Breakdown",
- "type": "array"
- },
- "geojson": {
- "description": "FSR polygons. Feature properties: fsr, band, color.",
- "properties": {
- "features": {
- "description": "Feature list.",
- "items": {
- "description": "RFC 7946 Feature — geometry + endpoint-specific properties.",
- "properties": {
- "geometry": {
- "additionalProperties": true,
- "description": "GeoJSON geometry (Polygon or MultiPolygon).",
- "title": "Geometry",
- "type": "object"
- },
- "properties": {
- "additionalProperties": true,
- "description": "Per-feature attributes — see the endpoint's example.",
- "title": "Properties",
- "type": "object"
- },
- "type": {
- "const": "Feature",
- "description": "Always 'Feature'.",
- "title": "Type",
- "type": "string"
- }
- },
- "required": [
- "type",
- "geometry",
- "properties"
- ],
- "title": "GeoJsonFeature",
- "type": "object"
- },
- "title": "Features",
- "type": "array"
- },
- "type": {
- "const": "FeatureCollection",
- "description": "Always 'FeatureCollection'.",
- "title": "Type",
- "type": "string"
- }
- },
- "required": [
- "type",
- "features"
- ],
- "title": "GeoJsonFeatureCollection",
- "type": "object"
- },
- "median_fsr": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Area-weighted median FSR (e.g. 1.5 = 1.5:1).",
- "title": "Median Fsr"
- }
- },
- "required": [
- "breakdown",
- "geojson"
- ],
- "title": "FsrControls",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Floor-space-ratio controls."
- },
- "hob": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Height-of-building controls summary + polygons.",
- "properties": {
- "geojson": {
- "description": "HOB polygons. Feature properties: height_m, units, band, color.",
- "properties": {
- "features": {
- "description": "Feature list.",
- "items": {
- "description": "RFC 7946 Feature — geometry + endpoint-specific properties.",
- "properties": {
- "geometry": {
- "additionalProperties": true,
- "description": "GeoJSON geometry (Polygon or MultiPolygon).",
- "title": "Geometry",
- "type": "object"
- },
- "properties": {
- "additionalProperties": true,
- "description": "Per-feature attributes — see the endpoint's example.",
- "title": "Properties",
- "type": "object"
- },
- "type": {
- "const": "Feature",
- "description": "Always 'Feature'.",
- "title": "Type",
- "type": "string"
- }
- },
- "required": [
- "type",
- "geometry",
- "properties"
- ],
- "title": "GeoJsonFeature",
- "type": "object"
- },
- "title": "Features",
- "type": "array"
- },
- "type": {
- "const": "FeatureCollection",
- "description": "Always 'FeatureCollection'.",
- "title": "Type",
- "type": "string"
- }
- },
- "required": [
- "type",
- "features"
- ],
- "title": "GeoJsonFeatureCollection",
- "type": "object"
- },
- "legend": {
- "description": "Area share per height band.",
- "items": {
- "description": "One legend band with its share of the mapped area.",
- "properties": {
- "color": {
- "description": "Hex colour for map styling.",
- "title": "Color",
- "type": "string"
- },
- "label": {
- "description": "Band label (e.g. '8.5–12m', '≤ 0.5:1').",
- "title": "Label",
- "type": "string"
- },
- "pct": {
- "description": "Share of mapped area in this band (%).",
- "title": "Pct",
- "type": "number"
- }
- },
- "required": [
- "label",
- "color",
- "pct"
- ],
- "title": "BandShare",
- "type": "object"
- },
- "title": "Legend",
- "type": "array"
- },
- "most_common_height_m": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Modal height limit across mapped zones (metres).",
- "title": "Most Common Height M"
- },
- "pct_most_common": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Share of zones at the modal height (%).",
- "title": "Pct Most Common"
- },
- "zones_mapped": {
- "description": "Number of height-control zones counted (RL reference levels >30m excluded).",
- "title": "Zones Mapped",
- "type": "integer"
- }
- },
- "required": [
- "zones_mapped",
- "legend",
- "geojson"
- ],
- "title": "HobControls",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "Height-of-building controls."
- }
- },
- "required": [
- "area_name",
- "area_level"
- ],
- "title": "SuburbBuildingControls",
- "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[SuburbBuildingControls]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SuburbBuildingControls_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety. The description adds a small behavioral detail ('band summaries') but does not explain what 'control polygons' implies about the output format or whether it returns geometry. It is not contradictory, so a 3 is appropriate.
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?
A single, compact sentence with zero filler. It is front-loaded with the core subject and avoids redundancy, making it efficient for an agent to parse.
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 tool with only one parameter and no output schema, the description is minimal but not fully complete. It lacks details on what 'band summaries' contain, whether the output is a map or tabular data, and any constraints on the suburb_name value. It is adequate for a simple query but leaves gaps.
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 mention the suburb_name parameter at all. While the parameter name is self-explanatory, the tool does not clarify expected format (e.g., exact name vs. code) or that it is a required input. This leaves the agent to infer.
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 clearly identifies the resource: height-of-building and floor-space-ratio control polygons with band summaries. It distinguishes from siblings like zoning_map by specifying the exact metrics, though it lacks an explicit verb like 'retrieve' or 'list'.
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 guidance on when to use this tool versus the many other suburbs_development_* alternatives. It does not mention that it requires a suburb_name or that it is for a specific suburb, nor does it contrast with zoning_map or development_all.
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.