Skip to main content
Glama

Microburbs Australian Property Data

Australia · NDIS participants

australia_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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "australia_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.

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 establish the safe, idempotent, non-destructive read profile, so the description is free to add the things annotations do not: a 5¢ per-call price, a suppression rule (councils with fewer than 11 participants removed), and the quarter-end period convention. These are real behavioral facts an agent would otherwise not know; only a note on response shape/pagination is missing.

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?

Purpose is front-loaded, followed by coverage, a doc pointer and price, which is a sensible order. The date range is stated twice in near-identical forms (quarter labels vs quarter-end dates), which is mildly redundant but also clarifying.

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 three-parameter read tool with no output schema, the definition covers what is measured, geographic granularity, temporal span, suppression policy, cost and where to find the full field list. The only gap is that sibling selection between this and the LGA/state variants is left implicit.

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 `from`, `to` and `fields` are already documented with accepted formats. The description adds the useful interpretation 'Period is the first day of the quarter' and an upper bound of 2026-06-30 for valid `to` values, but it does not explain `fields` beyond what the schema says, and the two date ranges quoted (Dec 2021–Jun 2026 vs Oct 2021–Apr 2026) are slightly ambiguous.

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 measure (number of people with an approved NDIS plan), the three geography levels (council area, state, Australia) and the cadence. Spelling out that it spans council areas, states and Australia implicitly distinguishes it from the LGA-only and states-only NDIS siblings, but it never explicitly names those alternatives.

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?

There is no explicit when-to-use or when-not-to-use statement, nor a pointer to the narrower LGA/state siblings. The stated coverage and the 'Current to 2026-06-30' note only imply the appropriate context, leaving the agent to infer routing.

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