Skip to main content
Glama

Microburbs Australian Property Data

State · NDIS participants

states_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": {
      "state": "<state>"
    },
    "name": "states_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.
stateYesState or territory abbreviation: nsw, vic, qld, sa, wa, tas, act or nt.
fieldsNoComma-separated subset of: participants. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds genuinely new operational context: a 5¢ per-call price, a small-area suppression rule (<11 participants), the period convention (first day of the quarter), and a currency date. It stops short of describing the response shape, but the annotation bar is met and exceeded.

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 before coverage details, price, and doc pointer; every sentence carries information. Slightly dense with a verbose coverage clause and a mild restatement between the opening sentence and the date-range sentence, but no filler.

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 time-series query with no output schema, the description supplies coverage, time bounds, suppression caveats, cost, and a pointer to the field list and method. The main remaining gap is that return-value structure (e.g. rows keyed by period and region with a participants field) is only implied by the schema's 'fields' parameter.

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 would be 3. The description goes beyond the schema by explaining that 'period' means the first day of the quarter, which disambiguates how from/to bound the series, and by explaining the suppression rule that affects which council areas appear in results.

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

Purpose5/5

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

Names a concrete metric (number of people with an approved NDIS plan), the geographies it is broken out by (council area, state, Australia), and the cadence (quarterly, Dec 2021–Jun 2026). This clearly separates it from the lga_ and australia_ NDIS siblings by the level of geography implied, and from the antidepressant/drug-use state series by subject matter.

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?

The coverage paragraph makes the intended scope clear (states/territories plus Australia, quarterly, bounded date range), so an agent can infer this is the state-level NDIS query. However, it never explicitly says when to use this versus lga_health_ndis_participants or australia_health_ndis_participants, nor does it state any exclusions, so selection is left 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