Microburbs Australian Property Data

LGA · Population

lga_population

Read-onlyIdempotent

Shown in the suburb report as the council-area lines on the 'Population' chart in the Demographics section.

The estimated resident population for the LGA at 30 June each year from 2001, with the change on the year before. Accepts the names /lga/list returns.

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

Input Schema

Name	Required	Description	Default
`lga_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.8/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 value annotations don't cover: the billing cost ('Price: 5¢ per call.') and the exact data vintage/measure, both of which affect whether and how an agent calls it.

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?

Short and mostly front-loaded, though the first sentence leads with UI placement rather than the data itself, which is the less actionable fact. Pricing is bolded and set apart, which reads cleanly. No significant waste.

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?

With no output schema, the description sensibly sketches the return: annual population from 2001 plus year-on-year change. Combined with the input-source hint and pricing, an agent has enough to call it correctly. Missing only edge-case behavior for unknown LGA names.

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 0% and the single parameter is bare, so the description carries the burden. It does that by saying it 'Accepts the names /lga/list returns,' which tells the agent where to source valid values and that the name format must match that listing. It does not state tolerance for case or partial matches.

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 a specific verb and resource: 'estimated resident population for the LGA at 30 June each year from 2001, with the change on the year before.' That is a precise data definition an agent can match to a request. It does not explicitly distinguish itself from siblings like lga_profile, so it stops short of a 5.

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?

Implied usage is decent: the report placement ('council-area lines on the Population chart in the Demographics section') and the pointer that valid inputs come from `/lga/list` both help an agent decide when to call it. There is no explicit when-not guidance or comparison against lga_profile.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Microburbs Australian Property Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?