Skip to main content
Glama

Microburbs Australian Property Data

Suburb · Employment by industry and occupation

suburbs_economy_employment_by_industry
Read-onlyIdempotent

What employed residents do for a living: head-counts and shares across 19 industries and 8 occupation groups, for every suburb and council area.

Coverage: About 8,800 suburbs and localities and 540 council areas across Australia (areas with fewer than 50 employed residents are left out); one snapshot at 10 August 2021. Current to 2021-08-10. Full description, field list and method: /v1/datasets/employment-by-industry.

Price: 10¢ 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_economy_employment_by_industry"
  }
}

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: employed_residents, ind_agriculture_forestry_fishing_count, ind_agriculture_forestry_fishing_pct, ind_mining_count, ind_mining_pct, ind_manufacturing_count, ind_manufacturing_pct, ind_utilities_count, ind_utilities_pct, ind_construction_count, ind_construction_pct, ind_wholesale_trade_count, ind_wholesale_trade_pct, ind_retail_trade_count, ind_retail_trade_pct, ind_accommodation_food_count, ind_accommodation_food_pct, ind_transport_postal_warehousing_count, ind_transport_postal_warehousing_pct, ind_media_telecommunications_count, ind_media_telecommunications_pct, ind_finance_insurance_count, ind_finance_insurance_pct, ind_rental_hiring_real_estate_count, ind_rental_hiring_real_estate_pct, ind_professional_scientific_technical_count, ind_professional_scientific_technical_pct, ind_administrative_support_count, ind_administrative_support_pct, ind_public_administration_safety_count, ind_public_administration_safety_pct, ind_education_training_count, ind_education_training_pct, ind_health_care_social_assistance_count, ind_health_care_social_assistance_pct, ind_arts_recreation_count, ind_arts_recreation_pct, ind_other_services_count, ind_other_services_pct, ind_industry_not_stated_count, ind_industry_not_stated_pct, occ_managers_count, occ_managers_pct, occ_professionals_count, occ_professionals_pct, occ_technicians_trades_count, occ_technicians_trades_pct, occ_community_personal_service_count, occ_community_personal_service_pct, occ_clerical_admin_count, occ_clerical_admin_pct, occ_sales_count, occ_sales_pct, occ_machinery_drivers_count, occ_machinery_drivers_pct, occ_labourers_count, occ_labourers_pct, occ_occupation_not_stated_count, occ_occupation_not_stated_pct. 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

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is cost and data limits: 10¢ per call and the exclusion of areas under 50 employed residents. Those are exactly the facts an agent needs before spending a call or retrying a null result; it stops short of describing response shape or empty-result behavior.

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 what the data contains, then coverage, then cost — the right order. Minor waste: 'one snapshot at 10 August 2021' and 'Current to 2021-08-10' say the same thing twice.

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?

No output schema exists, but the description conveys what a row contains (counts and shares by industry and occupation) and the coverage envelope. The one residual ambiguity — the description promises council areas while the required parameter is suburb_name — is partly rescued by the schema's exact-match instruction, so the definition is close to self-sufficient.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed per-parameter text, including the full comma-separated field list and the exact-match rule for suburb_name. The description's mention of 19 industries and 8 occupation groups helps the agent reason about the field families, so nothing meaningful is missing.

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 concrete subject ('what employed residents do for a living') and concrete measures ('head-counts and shares across 19 industries and 8 occupation groups') with a clear geographic scope. An agent can distinguish it from a generic dataset tool, though it never names the closest sibling (lga_economy_employment_by_industry) to draw the suburb-vs-LGA line 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 through coverage facts: the 50-employed-resident threshold tells the agent when the call will return nothing, and the single 2021 snapshot tells it not to expect time series. There is no explicit when-to-use/when-not guidance and no named alternative for council-level or occupation cross-tabs beyond the pointer to the docs page.

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