properties_surroundings_tenureABS Census 2021 tenure shares for each mesh block around the subject.
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": "Tenure mix (own / mortgage / rent / public) around the subject.",
- "example": {
- "as_of": "2021-08-10",
- "gnaf_pid": "GANSW704360755",
- "mbs": [
- {
- "mb": "10843090000",
- "mortgaged_pct": 39.9,
- "owned_outright_pct": 35.4,
- "property_count": 39,
- "public_housing_pct": 0,
- "rented_pct": 15.2
- },
- {
- "mb": "10842992000",
- "mortgaged_pct": 45.9,
- "owned_outright_pct": 36.3,
- "property_count": 21,
- "public_housing_pct": 0.6,
- "rented_pct": 6.6
- }
- ],
- "radius_m": 200
- },
- "properties": {
- "as_of": {
- "description": "Census anchor date (YYYY-MM-DD).",
- "title": "As Of",
- "type": "string"
- },
- "gnaf_pid": {
- "description": "The subject property's GNAF PID.",
- "title": "Gnaf Pid",
- "type": "string"
- },
- "mbs": {
- "description": "Per-mesh-block tenure shares, sorted by property count desc.",
- "items": {
- "additionalProperties": true,
- "description": "ABS Census 2021 tenure shares for one mesh block.",
- "properties": {
- "mb": {
- "description": "ABS 2021 mesh-block code.",
- "title": "Mb",
- "type": "string"
- },
- "mortgaged_pct": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Share of dwellings owned with a mortgage (%).",
- "title": "Mortgaged Pct"
- },
- "owned_outright_pct": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Share of dwellings owned outright (%).",
- "title": "Owned Outright Pct"
- },
- "property_count": {
- "description": "Properties inside the search box that sit in this mesh block.",
- "title": "Property Count",
- "type": "integer"
- },
- "public_housing_pct": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Share of dwellings in public/social housing (%).",
- "title": "Public Housing Pct"
- },
- "rented_pct": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Share of dwellings rented privately (%).",
- "title": "Rented Pct"
- }
- },
- "required": [
- "mb",
- "property_count"
- ],
- "title": "MbTenure",
- "type": "object"
- },
- "title": "Mbs",
- "type": "array"
- },
- "radius_m": {
- "description": "Radius of the search box around the subject, metres.",
- "title": "Radius M",
- "type": "integer"
- }
- },
- "required": [
- "gnaf_pid",
- "radius_m",
- "as_of",
- "mbs"
- ],
- "title": "SurroundingTenure",
- "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[SurroundingTenure]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SurroundingTenure_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety and side effects. The description adds the data source (ABS Census 2021) and granularity (each mesh block), which is useful, but it does not disclose return shape, tenure categories, or any quirks. This is adequate given the strong annotation coverage.
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: one sentence states the data product and granularity, and a second sentence gives the price. Information is front-loaded and no words are wasted.
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 tool, the description provides the essential context: what data, what geography, and price. However, there is no output schema, and the description does not enumerate the tenure categories or the exact output format, leaving some ambiguity for an agent.
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?
There is a single required parameter, gnaf_id, with 0% schema description coverage. The description never explains that gnaf_id identifies the subject property or how it should be formatted. The parameter name is somewhat self-explanatory, but the description adds no semantic value beyond the schema.
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: ABS Census 2021 tenure shares for each mesh block around the subject, with the 200 m scope in the title. It distinguishes from suburb-level tenure tools by specifying mesh-block granularity, though it lacks an explicit verb and does not name a sibling.
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 is given on when to use this tool versus alternatives such as properties_context_mesh_blocks or suburbs_demographics_tenure. There are no prerequisites, exclusions, or context about which property identifier is expected. Only the price is mentioned.
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.