Skip to main content
Glama

Microburbs Australian Property Data

LGA · NDIS participants

lga_health_ndis_participants
Read-onlyIdempotent

Number of people with an approved National Disability Insurance Scheme (NDIS) plan living in each council area, state and Australia, every quarter from December 2021 to June 2026.

Coverage: About 510 council areas (councils with fewer than 11 participants are suppressed), all 8 states and territories, and Australia; quarterly from October 2021 (December 2021 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/ndis-participants.

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

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: participants. 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 closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: small councils with fewer than 11 participants are suppressed, period is the first day of the quarter, data is current to 2026-06-30, and each call costs 5¢. It does not describe the response shape, though there is effectively one field.

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 metric and geography, then the operational constraints and price. It drifts into mild redundancy, restating the date range twice (Dec 2021–Jun 2026 in prose, then Oct 2021–Apr 2026 with quarter-end parentheticals), which an agent must reconcile unnecessarily.

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 single-metric read tool with full schema coverage and annotations, this is close to complete: geography coverage, temporal bounds, suppression rule, currency date, price and a documentation pointer are all present. The only real gap is that it never explicitly positions itself against the state and national NDIS siblings.

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/fields/lga_name including accepted date formats and the pointer to /v1/lga/list. The description reinforces a few constraints (quarter-start semantics, the covered period range) but adds no new per-parameter meaning, so the baseline 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 first sentence names the exact metric (approved NDIS participants), the resolution (each council area, state and Australia) and the cadence (quarterly). An agent can tell what data comes back. It stops short of a 5 because it never states that sibling tools like states_health_ndis_participants or australia_health_ndis_participants cover the same metric at other geographies.

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 rather than stated: the coverage paragraph tells the agent this tool spans LGA/state/national levels and Oct 2021–Jun 2026, which lets it infer fit, and the 5¢ price warns against careless calls. But there is no explicit when-to-use vs when-not or named alternative, leaving routing to the siblings to inference.

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