Skip to main content
Glama

Microburbs Australian Property Data

LGA · Welfare payment recipients

lga_economy_welfare_payments
Read-onlyIdempotent

Number of people receiving each government income-support payment (Age Pension, disability, JobSeeker, youth, parenting, carer, family tax benefit, rent assistance and concession cards) by council area and postcode, per quarter for the last three years.

Coverage: 543 council areas and about 2,630 postcodes across Australia; quarters from July 2023 (September 2023 quarter-end) to April 2026 (June 2026 quarter-end). Period is the first day of the quarter. Current to 2026-06-30. Full description, field list and method: /v1/datasets/welfare-payments.

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

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: age_pension, disability_support_pension, jobseeker_payment, youth_allowance, youth_allowance_student_and_apprentice, youth_allowance_other, parenting_payment_single, parenting_payment_partnered, carer_payment, carer_allowance, carer_allowance_child_health_care_card_only, family_tax_benefit_a, family_tax_benefit_b, commonwealth_rent_assistance, austudy, abstudy_living_allowance, abstudy_non_living_allowance, special_benefit, pension_concession_card, commonwealth_seniors_health_card, health_care_card, low_income_card. 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.8/5.0
Behavior4/5

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

Annotations already establish a safe, read-only, idempotent, closed-world query. The description adds genuinely new context beyond them: the 5¢ per-call price, the exact data coverage (543 LGAs, ~2,630 postcodes), and the currency cut-off of 2026-06-30. It stops short of saying whether results are paginated or capped for large LGAs.

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 'what', then coverage, then a documentation pointer, then price — a sensible ordering for an agent deciding whether to call. Dense but not padded; the long payment enumeration and duplicated coverage-and-price lines cost a little length without adding choice.

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 filtered analytical query with full schema documentation, the description supplies grain (quarter), units (number of recipients), spatial dimensions, temporal bounds, and cost. The notable gap is the return shape — no output schema exists and no hint of whether rows are per-postcode, per-quarter, or aggregated.

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 coverage is 100%, so the baseline is 3; the description clears it by clarifying that 'Period is the first day of the quarter', which pins down how `from`/`to` resolve against the quarterly grain. The parenthetical expansion of payment categories also gives the agent a plain-language map to the `fields` enum values. It still leaves the accepted format set entirely to the schema.

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?

States a specific verb-ish resource: counts of people receiving each named income-support payment, broken down by council area and postcode, quarterly for three years. The enumerated payment list leaves no doubt about scope. It does not, however, separate itself from the sibling `postcodes_economy_welfare_payments`, and the phrase 'by council area and postcode' is slightly at odds with `lga_name` being the required parameter.

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: the tool returns welfare-recipient counts for a given LGA over a period. There is no statement of when to prefer this over the postcode-level sibling, nor any exclusion or prerequisite guidance. The pointer to `/v1/datasets/welfare-payments` gives the agent somewhere to look, but pushes the real guidance off-tool.

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