Microburbs Australian Property Data

by au.com.microburbs

Overview Discussions Admin

Suburb · Steep terrain

suburbs_risks_slope

Read-onlyIdempotent

Shown in the suburb report as the 'Steep terrain' card in the Risks section.

Median / 90th-percentile property gradient and share of steep (>10°) properties.

Price: 10¢ per call.

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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_risks_slope"
  }
}

Input Schema

Name	Required	Description	Default
`suburb_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedOutput 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": "Terrain gradient across the suburb's properties (degrees).",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Belmont North",
-            "median_slope_deg": 4.43,
-            "n_properties": 2727,
-            "p90_slope_deg": 8.29,
-            "steep_pct": 4.44,
-            "steep_threshold_deg": 10
-          },
-          "properties": {
-            "area_level": {
-              "const": "suburb",
-              "description": "Always 'suburb'.",
-              "title": "Area Level",
-              "type": "string"
-            },
-            "area_name": {
-              "description": "Canonical ABS SAL suburb name.",
-              "title": "Area Name",
-              "type": "string"
-            },
-            "median_slope_deg": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Median property gradient (degrees).",
-              "title": "Median Slope Deg"
-            },
-            "n_properties": {
-              "description": "Properties with a terrain sample.",
-              "title": "N Properties",
-              "type": "integer"
-            },
-            "p90_slope_deg": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "90th-percentile property gradient (degrees).",
-              "title": "P90 Slope Deg"
-            },
-            "steep_pct": {
-              "anyOf": [
-                {
-                  "type": "number"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Share of properties steeper than the threshold (%).",
-              "title": "Steep Pct"
-            },
-            "steep_threshold_deg": {
-              "description": "Gradient threshold used for steep_pct (degrees).",
-              "title": "Steep Threshold Deg",
-              "type": "number"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "n_properties",
-            "steep_threshold_deg"
-          ],
-          "title": "SlopeProfile",
-          "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[SlopeProfile]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SlopeProfile_"
-}New value: +null

First observedSep 14, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is supplementary — and it delivers useful non-schema context: the per-call cost (10¢) and the specific metrics returned. It does not cover behavior on unknown suburb names or empty results, which keeps it below a 5.

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?

Three tight sentences that front-load the report location and then the metrics, with pricing last. The 'Shown in the suburb report as the Steep terrain card' line partly restates the title but still anchors where the number appears.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool with annotations covering safety and no output schema requiring explanation, the description covers purpose, metrics, and cost. The missing piece is the suburb_name input format, which is undocumented in both schema and description.

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?

Only one parameter exists and schema description coverage is 0%, so the description must compensate; it names the suburb scope implicitly but never specifies the expected suburb_name format (e.g., whether state or postcode is required, or matching rules). Adequate for an obvious single parameter, but with a real gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and metrics: median/90th-percentile property gradient and share of steep (>10°) properties, scoped to a suburb's Risks report. It is clear what the tool returns, though it never distinguishes itself from property-level terrain siblings such as properties_environment_terrain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage context is that it appears as the 'Steep terrain' card in a suburb report; there is no explicit instruction on when to call it versus related risk or terrain tools, and no prerequisites or exclusions are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Microburbs Australian Property Data 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?