Microburbs Australian Property Data

Suburb · Liquor licences

suburbs_area_stats_liquor_licences

Read-onlyIdempotent

Current liquor licences per suburb by type (pubs, restaurants, bottle shops, clubs, producers), late-night licences and a per-address density, for Victoria and New South Wales.

Coverage: Victoria (as at 31 Aug 2026) and New South Wales (as at 7 Jun 2024). Other states return no data. Current to 2026-08-31. Full description, field list and method: /v1/datasets/liquor-licences.

Price: 3¢ 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_area_stats_liquor_licences"
  }
}

Input Schema

Name	Required	Description
`to`	No	Last period to include, same formats as `from`.
`from`	No	First period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
`fields`	No	Comma-separated subset of: licences_total, pubs_hotels, restaurants_on_premises, bottle_shops, clubs, producers_wholesalers, limited_temporary, other, late_night_3am, licences_per_1000_addresses. Omit for all.
`suburb_name`	Yes	Suburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

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 declare the safe read-only/idempotent/closed-world profile, so the description's job is to add context — and it does: per-call pricing (3¢), as-at dates for each state's data (VIC 31 Aug 2026, NSW 7 Jun 2024), the last-updated date, and the fact that unsupported states yield empty results. It doesn't discuss response shape or whether `from`/`to` matter given a single dated snapshot, which is the one remaining behavioral ambiguity.

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?

Front-loaded with the core capability in one sentence, then clearly separated Coverage and Price blocks. Every line carries usable information (scope, staleness, price, doc pointer) with no filler.

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 compensates by naming the metrics returned, the geographic coverage, and the dataset doc for the field list and method. The only gap is how `from`/`to` interact with a single as-at snapshot and what an empty result looks like, which an agent might need before calling.

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%, so all four parameters (including the `fields` enumeration and `from`/`to` formats) are already documented in structured data. The description's licence-type list duplicates the `fields` enum rather than adding syntax or semantics beyond it, so the 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?

The description states a specific verb+resource — current liquor licences per suburb, broken down by licence type, plus late-night licences and per-address density — and scopes it to Victoria and NSW. Against a sibling set of many other `suburbs_area_stats_*` topic tools, the subject matter makes the distinction immediate.

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?

It gives clear when-not-to-use guidance ('Other states return no data'), a required input format rule (suburb name exactly as /v1/suburbs/list returns it, e.g. `St Kilda (Vic.)`), and a pointer to the dataset page for full docs. It stops short of naming an alternative sibling tool for other states or other topics, so routing is implied rather than explicit.

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?