Skip to main content
Glama

Microburbs Australian Property Data

Suburb · Food and drink places

suburbs_amenities_food_and_drink
Read-onlyIdempotent

Cafes, restaurants, takeaway, bakeries, pubs and bars, bottle shops and breweries or wineries: counts in the suburb, rates per 1,000 residents and distance from the suburb centre to the nearest of each.

Coverage: All Australian suburbs and localities. Current to 2026-10-01. Full description, field list and method: /v1/datasets/food-and-drink.

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_amenities_food_and_drink"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period to include, same formats as `from`.
fromNoFirst period to include: 2020, 2020-Q3, 2020-07 or 2020-07-01.
fieldsNoComma-separated subset of: count_takeaway, per_1000_takeaway, nearest_km_takeaway, count_cafes, per_1000_cafes, nearest_km_cafes, count_restaurants, per_1000_restaurants, nearest_km_restaurants, count_bakeries, per_1000_bakeries, nearest_km_bakeries, count_pubs_bars, per_1000_pubs_bars, nearest_km_pubs_bars, count_bottle_shops, per_1000_bottle_shops, nearest_km_bottle_shops, count_breweries_wineries, per_1000_breweries_wineries, nearest_km_breweries_wineries, count_total, per_1000_total, per_km2_total. Omit for all.
suburb_nameYesSuburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 safety is covered. The description adds genuinely non-redundant behavior: geographic/period coverage (all Australian suburbs, current to 2026-10-01) and a per-call price of 5¢, which matters for an agent deciding whether to loop over many suburbs. It does not describe response shape or truncation/pagination for large field requests.

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?

Front-loaded with the substantive content (what is measured and for which categories), followed by a compact coverage/metric block and a docs pointer. The category list is long but each term maps to a real field family, and the bolded price line is short and high-value. Minor redundancy between 'Coverage' and the dataset link.

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 conveying return content, and it does so reasonably by stating the three metric forms (count, rate per 1,000, distance from suburb centre to nearest). The explicit documentation endpoint compensates for anything omitted. What is missing is guidance on time-series behavior when from/to are supplied and on how multiple metrics are returned.

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 the schema already documents from/to formats, the exact field enumerations and the exact-match requirement for suburb_name. The description adds only the conceptual framing (counts, per-1,000 rates, nearest distance), which lightly anchors the field names but supplies no new syntax or constraints. Baseline 3 applies.

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?

The description names a specific resource (food and drink places in a suburb) and enumerates the exact subcategories covered (cafes, restaurants, takeaway, bakeries, pubs and bars, bottle shops, breweries/wineries), plus the three metric types produced. It is clearly distinguishable from area-stat and property siblings by its amenity focus, though it never names a sibling directly.

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 only implied: an agent can infer 'use this for food and drink amenity metrics for an Australian suburb.' There is no explicit when-to-use / when-not, no guidance on choosing between this and the other suburbs_amenities_* tools, and no stated prerequisite such as resolving the suburb name via /v1/suburbs/list first.

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