Skip to main content
Glama
Sign In

Microburbs Australian Property Data

by au.com.microburbs
OverviewDiscussionsAdmin

LGA · Same-sex couples

lga_area_stats_same_sex_couples
Read-onlyIdempotent

How many couple families are same-sex couples, and what share of couples that is: male and female couples, and those raising children, for every sizeable suburb and council area.

Coverage: About 5,300 suburbs and localities and 512 council areas across Australia, in all states and territories (areas with fewer than 100 couple families are left out); one snapshot at 10 August 2021. Current to 2021-08-10. Full description, field list and method: /v1/datasets/same-sex-couples.

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": {
      "lga_name": "<lga_name>"
    },
    "name": "lga_area_stats_same_sex_couples"
  }
}

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: couple_families_total, same_sex_couples_count, same_sex_couples_pct, male_same_sex_couples_count, male_same_sex_couples_pct, female_same_sex_couples_count, female_same_sex_couples_pct, same_sex_couples_with_children_count, same_sex_couples_with_children_pct, male_same_sex_couples_with_children_count, female_same_sex_couples_with_children_count. Omit for all.
lga_nameYesCouncil (LGA) name exactly as /v1/lga/list returns it, e.g. `Lake Macquarie`.

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 the description adds genuinely new behavioral facts: a per-call price of 5¢, a fixed 10 August 2021 snapshot, and the exclusion of areas with fewer than 100 couple families. The response shape is not described, but for a read-only data lookup the cost and coverage disclosures are the material additions.

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?

Well front-loaded: the question the dataset answers comes first, then coverage, then the docs pointer, then price. Minor waste in restating the snapshot twice ('10 August 2021' and 'Current to 2021-08-10').

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 aggregate query with full schema coverage and no output schema, the description supplies dataset size, geography, time coverage, minimum-size exclusion, pricing, and a link to the full field list and method. The remaining gap is that it does not indicate the returned row structure or whether one or many rows come back per LGA.

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 coverage is 100%, so the schema already documents from/to, the full field list, and the requirement that lga_name match /v1/lga/list exactly. The description adds no parameter-level meaning beyond that, so the baseline of 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 clearly names the resource and the measures: counts and shares of same-sex couples, split male/female, plus those with children, at council-area level. It distinguishes itself from its suburb-level sibling only implicitly through the tool name and the 'council area' mention, and the phrase 'for every sizeable suburb and council area' actually blurs the LGA-only scope rather than sharpening it.

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 coverage block: use this for LGA-level same-sex couple statistics as at August 2021, with areas under 100 couple families excluded. There is no explicit when-to-use vs. when-not guidance and no named alternative (e.g. the suburbs variant or area_stats_values) is offered for finer geography.

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