Skip to main content
Glama

Microburbs Australian Property Data

Property · All valuation outputs — bundle

properties_valuation_all
Read-onlyIdempotent

Price: 10¢ per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gnaf_idYes

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": [
      -        {
      -          "description": "All valuation outputs in one call. Today: just the AVM (which\nnow includes confidence_score inline). Kept as a bundle so future\nvaluation outputs — rental AVM, off-market signals — slot in\nwithout a new endpoint.",
      -          "properties": {
      -            "avm": {
      -              "anyOf": [
      -                {
      -                  "description": "Automated valuation: point estimate + 80% prediction interval +\nconfidence score derived from the interval width.",
      -                  "example": {
      -                    "predicted_price": 876651,
      -                    "predicted_price_high": 1183479,
      -                    "predicted_price_low": 569823,
      -                    "prediction_date": "2026-04-20"
      -                  },
      -                  "properties": {
      -                    "confidence_score": {
      -                      "anyOf": [
      -                        {
      -                          "type": "integer"
      -                        },
      -                        {
      -                          "type": "null"
      -                        }
      -                      ],
      -                      "description": "0–100. The valuation model's own calibrated confidence in this estimate — higher means the model is more certain. Read alongside `predicted_price_low` / `predicted_price_high` for the range.",
      -                      "title": "Confidence Score"
      -                    },
      -                    "predicted_price": {
      -                      "description": "Point estimate, AUD.",
      -                      "title": "Predicted Price",
      -                      "type": "number"
      -                    },
      -                    "predicted_price_high": {
      -                      "description": "Upper bound of the 80% prediction interval, AUD.",
      -                      "title": "Predicted Price High",
      -                      "type": "number"
      -                    },
      -                    "predicted_price_low": {
      -                      "description": "Lower bound of the 80% prediction interval, AUD.",
      -                      "title": "Predicted Price Low",
      -                      "type": "number"
      -                    },
      -                    "prediction_date": {
      -                      "description": "Date the model produced this estimate. AVMs are refreshed in batches; not on demand.",
      -                      "title": "Prediction Date",
      -                      "type": "string"
      -                    }
      -                  },
      -                  "required": [
      -                    "predicted_price",
      -                    "predicted_price_low",
      -                    "predicted_price_high",
      -                    "prediction_date"
      -                  ],
      -                  "title": "AvmEstimate",
      -                  "type": "object"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "title": "ValuationAll",
      -          "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[ValuationAll]",
      -  "type": "object",
      -  "x-fastmcp-top-level-schema": "ApiResponse_ValuationAll_"
      -}New value: +null
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent already knows this is a safe read operation. The description adds only the pricing detail (10¢ per call), which is useful but minimal. It does not disclose the response size, potential for large payloads, or that all valuation outputs are included.

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?

The description is very short (one phrase), but it is not misleading; it is minimal yet honest. However, it fails to provide essential functional information, so the conciseness is a tradeoff for completeness.

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

Completeness2/5

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

Given the tool returns a comprehensive bundle of valuation outputs, the description is incomplete. An agent needs to know what data is included, the parameter format, and any constraints. With no output schema, the description should explain the return value, but it only states the price.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has only one parameter, gnaf_id, with no description and 0% schema coverage. The tool description does not explain what gnaf_id is (likely a G-NAF identifier for a property) or how to obtain it. Since schema coverage is 0%, the description needed to clarify the parameter, but it does not.

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

Purpose3/5

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

The title and tool name indicate a bundle of valuation outputs, but the description only states the price, not what the tool actually does. It does not mention that it returns all valuation data for a property. An agent can infer it aggregates valuation outputs, but it is not explicit.

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?

No guidance on when to use this tool vs. the individual valuation tools (e.g., properties_valuation_avm) or other sibling tools. The description does not mention that it is a cost-effective bundle for comprehensive valuation data, and no exclusions or alternatives are provided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources