Skip to main content
Glama

Microburbs Australian Property Data

LGA · Long-term health conditions

lga_area_stats_health_conditions
Read-onlyIdempotent

How many residents live with arthritis, asthma, cancer, dementia, diabetes, heart disease, a mental health condition, stroke and other long-term conditions, and how many have more than one, for every suburb and council area.

Coverage: About 11,000 suburbs and localities and 545 council areas across Australia, in all states and territories (areas with too few people or homes for reliable figures are left out); one snapshot at 10 August 2021. Current to 2021-08-10. Full description, field list and method: /v1/datasets/health-conditions.

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

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: total_population, arthritis_count, arthritis_pct, asthma_count, asthma_pct, cancer_count, cancer_pct, dementia_count, dementia_pct, diabetes_count, diabetes_pct, heart_disease_count, heart_disease_pct, kidney_disease_count, kidney_disease_pct, lung_condition_count, lung_condition_pct, mental_health_condition_count, mental_health_condition_pct, stroke_count, stroke_pct, other_condition_count, other_condition_pct, no_condition_count, no_condition_pct, any_named_condition_count, any_named_condition_pct, no_named_condition_count, no_named_condition_pct, one_named_condition_count, one_named_condition_pct, two_named_conditions_count, two_named_conditions_pct, three_plus_named_conditions_count, three_plus_named_conditions_pct, not_stated_count, not_stated_pct. 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.5/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 the safety profile is covered. The description adds genuinely useful behavior beyond that: dataset scale (≈11,000 suburbs, 545 council areas), the exclusion rule for unreliable small areas, a single snapshot at 2021-08-10 with a 'current to' date, and a per-call price of 5¢ — cost disclosure is valuable for an agent deciding whether to call repeatedly.

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?

The key content is front-loaded and there is no filler; the coverage, currency and price lines are each doing distinct work. The opening sentence is an overlong run-on list, and the raw internal path `/v1/datasets/health-conditions` is slightly odd for an agent-facing doc.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-required-parameter stats tool with no output schema, the description supplies what an agent actually needs: what is measured, the geographic unit and universe, the temporal snapshot (which implicitly explains why `from`/`to` have little effect), the small-area exclusion, and where to find the field list and method.

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 `from`, `to`, `fields` and `lga_name` are already fully documented, which sets the baseline at 3. The description's enumeration of conditions loosely maps to the field list and hints at the multi-condition fields, but adds no syntax, default or edge-case guidance for the period filters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The data resource is unmistakable: counts of residents with arthritis, asthma, cancer, dementia, diabetes, heart disease, mental health conditions, stroke and comorbidities. However, the phrase 'for every suburb and council area' is misleading for a tool whose name and required `lga_name` parameter restrict it to LGA level, and it blurs the boundary with the `suburbs_area_stats_health_conditions` sibling 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 through the coverage statement (areas with too few people excluded) and the pointer to `/v1/datasets/health-conditions` for method details, but there is no explicit when-to-use guidance and no statement about when to prefer the suburb-level sibling or `lga_health_ndis_participants` instead.

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