Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · High-voltage power lines

suburbs_risks_hv_power_lines
Read-onlyIdempotent

Shown in the suburb report as the 'High-voltage power lines' card in the Risks section.

Whether high-voltage transmission lines cross the suburb, how many, and the highest voltage class (overhead lines only).

Price: 5¢ 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_hv_power_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
suburb_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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": "High-voltage electricity transmission lines crossing the suburb.",
-          "example": {
-            "area_level": "suburb",
-            "area_name": "Blacktown",
-            "line_count": 6,
-            "max_kv": 132,
-            "overhead_only": true,
-            "present": true
-          },
-          "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"
-            },
-            "line_count": {
-              "description": "Transmission-line features intersecting the suburb boundary.",
-              "title": "Line Count",
-              "type": "integer"
-            },
-            "max_kv": {
-              "anyOf": [
-                {
-                  "type": "integer"
-                },
-                {
-                  "type": "null"
-                }
-              ],
-              "description": "Highest voltage class among the intersecting lines, in kV (null when none intersect or the source carries no voltage class).",
-              "title": "Max Kv"
-            },
-            "overhead_only": {
-              "const": true,
-              "description": "Underground segments are excluded from the count — only overhead (and unclassified) transmission is counted.",
-              "title": "Overhead Only",
-              "type": "boolean"
-            },
-            "present": {
-              "description": "True when at least one HV line crosses the suburb.",
-              "title": "Present",
-              "type": "boolean"
-            }
-          },
-          "required": [
-            "area_name",
-            "area_level",
-            "present",
-            "line_count",
-            "overhead_only"
-          ],
-          "title": "SuburbHvPowerLines",
-          "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[SuburbHvPowerLines]",
-  "type": "object",
-  "x-fastmcp-top-level-schema": "ApiResponse_SuburbHvPowerLines_"
-}New value: +null
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds real value annotations cannot: the coverage limitation to overhead lines only and an explicit 5¢ per-call cost, which affects invocation budgeting. It omits whether a suburb without lines returns nulls or zeros.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short blocks: where it appears, what it measures, what it costs. The output content and the scope caveat are front-loaded, and the pricing line earns its place because it materially affects whether an agent calls it.

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

Completeness4/5

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

With no output schema, the description carries the burden of return semantics and does so adequately by naming the three returned facts plus the overhead-only restriction. For a one-parameter read tool this is close to complete; only the empty/no-lines behavior and output shape remain unspecified.

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?

Schema coverage is 0% and the description says nothing about suburb_name — no format, no note on whether a state or postcode qualifier is needed, no hint about ambiguity between duplicate suburb names. The single parameter is largely self-explanatory, so the gap is modest rather than fatal.

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?

States a specific resource and scope: whether high-voltage transmission lines cross the suburb, the count, and the highest voltage class, restricted to overhead lines. The 'suburb report ... card' framing signals it is the suburb-level counterpart to property-level risk tools, though it never names that sibling explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'shown in the suburb report as the ... card in the Risks section,' which tells an agent this is a suburb-granularity risk lookup. There is no explicit when-to-use/when-not guidance and no mention of how it relates to suburbs_risks_all or properties_risks_hv_power_line.

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 toolsInspect
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