Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

Suburb · Arts, culture and entertainment

suburbs_amenities_arts_and_entertainment
Read-onlyIdempotent

Cinemas, theatres and concert halls, museums and art galleries: 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/arts-and-entertainment.

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

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_cinemas, per_1000_cinemas, nearest_km_cinemas, count_theatres, per_1000_theatres, nearest_km_theatres, count_museums, per_1000_museums, nearest_km_museums, 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.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds genuinely useful non-schema context: a per-call price (5¢), the currency of the data (current to 2026-10-01), the geographic coverage, and a pointer to the full dataset doc. It still doesn't describe response shape or pagination, but nothing contradicts the annotations.

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 resource and measures in one sentence, then coverage, then price, then the canonical doc link. Every sentence carries distinct information and none is wasted.

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 read-only single-suburb metrics tool with no output schema, the description plus a fully documented schema and a dataset reference give an agent enough to call it correctly. Only the row/grain of the response is left implicit.

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

Parameters4/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 carries the parameters. The description adds meaning the schema does not: that the `nearest_km_*` fields measure distance from the suburb centre to the nearest facility, which is otherwise opaque from the field names alone.

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?

Names the concrete resources (cinemas, theatres, concert halls, museums, art galleries) and the measures returned (counts, rates per 1,000 residents, distance to nearest), so an agent knows exactly what data comes back. It is distinguishable from the other amenities siblings by subject matter, though it never names an alternative tool explicitly.

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 implied by the framing (query amenity metrics for a given suburb) and the coverage note says it applies to all Australian suburbs and localities. There is no explicit when-to-use/when-not-to-use guidance, no mention of when a sibling such as parks or food-and-drink would be the better call, and no prerequisites stated.

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 toolsInspect
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