Skip to main content
Glama

Microburbs Australian Property Data

LGA · Unemployment by council area

lga_economy_unemployment
Read-onlyIdempotent

Quarterly unemployment rate, number unemployed and labour force for every local council area since late 2010. Modelled estimates.

Coverage: 541 council areas, all states and territories; December quarter 2010 to June quarter 2026. Current to 2026-06-30. Full description, field list and method: /v1/datasets/unemployment-lga.

Price: 3¢ 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_economy_unemployment"
  }
}

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: unemployment_rate, unemployed_persons, labour_force. 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.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world, non-destructive), yet the description still adds real behavioral context: these are modelled rather than measured estimates, the series currency date (2026-06-30), the panel size (541 areas) and a per-call price of 3¢. It stops short of describing pagination or row/response limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what the tool returns, then a labelled coverage block, then the doc link and price — three short, scannable chunks with no filler. Each element (modelled-estimate warning, date range, currency, cost) carries decision-relevant information.

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 4-parameter read-only dataset query with no output schema, the description supplies the measure list, geographic scope, temporal bounds, data currency, cost and a documentation path. The main remaining gap is return shape/size (row counts, ordering) and how to resolve `lga_name`, the latter of which is at least covered in the schema.

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 the schema already explains `from`/`to` formats, the comma-separated `fields` subset and the exact-match `lga_name`. The description adds only the pointer to `/v1/datasets/unemployment-lga` for the field list and method, so 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?

States the specific measures (unemployment rate, number unemployed, labour force), the geography (every local council area), and the cadence (quarterly) with a start period. It is clearly distinct in resource terms from suburb-level and area-stats siblings, though it never names an alternative tool 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 by the coverage statement (LGA-level, quarterly, 2010 onwards), so an agent can infer this is the LGA unemployment series rather than a suburb or industry series. There is no explicit when-to-use/when-not-to-use guidance and no named alternative such as the suburb unemployment sibling.

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