Microburbs Australian Property Data

List datasets

datasets

Read-onlyIdempotent

Every dataset in the catalog with its endpoints, price and as-of date. Use it to find what we hold for a theme or a geography level, then call /v1/datasets/{slug} for the method and field list.

Price: 1¢ per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "datasets"
  }
}

Input Schema

Name	Required	Description
`level`	No	suburb, lga or block.
`query`	No	Words that must all appear in the name or description.
`category`	No	crime, economy, environment, schools, planning, market, demographics, transport or health.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's main contribution is the pricing disclosure — '1¢ per call' — which is real context an agent cannot get from structured fields. It also discloses the shape of the response (endpoints, price, as-of date). No permissions, pagination, or result-size guidance is given, so not 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.

Conciseness5/5

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

Three short sentences, front-loaded with what is returned, then how to use it, then the cost. Nothing is redundant and the cost line is isolated for visibility.

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?

For a zero-required-parameter list tool with no output schema, the description covers what is returned, the searching intent, the follow-up path, and cost. Only pagination/result limits and whether all categories are always returned are missing, which are minor gaps.

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 description coverage is 100%, with each of level, query and category already documented, including category's enumerated values. The description only echoes the concepts of theme and geography level; it adds no syntax, matching behavior (AND semantics for query words) or example values beyond the schema. Baseline 3 applies.

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

Purpose5/5

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

States the resource ('every dataset in the catalog') and enumerates the returned fields (endpoints, price, as-of date). It also separates itself from the detail endpoint by saying the method/field list lives at `/v1/datasets/{slug}`, so an agent can tell the two apart without opening schemas.

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

Usage Guidelines4/5

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

Gives a clear positive trigger — finding what is held for a theme or geography level — and prescribes the follow-up call for method and field detail. It does not state when not to use the tool or name alternatives by their tool names, so it stops short of full routing guidance.

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?