Skip to main content
Glama

Microburbs Australian Property Data

Suburb · Federal election results

suburbs_demographics_federal_election_results
Read-onlyIdempotent

How each suburb voted at the 2019, 2022 and 2025 federal elections (House of Representatives): first-preference share by party, two-party-preferred Labor v Coalition, swings, informal vote and the electorate. Also state and national totals with turnout.

Coverage: About 7,500 suburbs per election (every suburb with at least 100 allocated formal votes), all 8 states and territories, and Australia; federal elections 2019, 2022 and 2025. Current to 2025-05-03. Full description, field list and method: /v1/datasets/election-results-federal.

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": {
      "suburb_name": "<suburb_name>"
    },
    "name": "suburbs_demographics_federal_election_results"
  }
}

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: formal_votes, informal_votes, informal_pct, labor_votes, coalition_votes, greens_votes, one_nation_votes, independent_votes, other_votes, labor_pct, coalition_pct, greens_pct, one_nation_pct, independent_pct, other_pct, tpp_labor_votes, tpp_coalition_votes, tpp_labor_pct, tpp_coalition_pct, labor_swing, coalition_swing, greens_swing, one_nation_swing, independent_swing, tpp_labor_swing, main_division, main_division_share_pct, divisions, enrolment, turnout_pct. Omit for all.
suburb_nameYesSuburb name exactly as /v1/suburbs/list returns it, e.g. `Bondi` or `St Kilda (Vic.)`.

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, non-destructive, closed-world), so the description earns credit for adding non-annotation facts: a 5¢ per-call price, a 100-formal-vote inclusion threshold that means small suburbs are absent, a currency date of 2025-05-03, and a pointer to the method page. It does not discuss response shape or pagination, but with no output schema and a field list available in the schema, that gap is small.

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?

The measure list is front-loaded and the coverage and price blocks are visually separated, so an agent can skim. A couple of phrases (“Also state and national totals with turnout”) are ambiguous about whether this tool returns them or a sibling does, which is wasted precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-required-parameter data tool with a fully documented schema and no output schema, the description supplies measures, geography, time range, coverage caveats, freshness, cost, and a docs pointer. Nothing an agent needs in order to call it correctly is missing.

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 carries the parameter documentation and baseline is 3. The description adds only the requirement that suburb_name match /v1/suburbs/list output, which the schema also states. Notably it does not reconcile the schema's date-style `from`/`to` examples (2020, 2020-Q3) with the description's election-year framing, leaving that mapping unexplained in both places.

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 description names a specific verb and resource (“how each suburb voted”) and enumerates the returned measures (first-preference share, two-party-preferred, swings, informal vote, electorate), which clearly separates it from the demographics siblings. It stops short of explicitly contrasting itself with states_/australia_demographics_federal_election_results, and the trailing “Also state and national totals with turnout” blurs the boundary with those siblings.

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 use conditions are only implicit: suburb-level geography, elections 2019/2022/2025. Coverage statistics (“about 7,500 suburbs … every suburb with at least 100 allocated formal votes”) hint at when the tool is applicable but are framed as data scope rather than guidance. There is no explicit “use this instead of X when Y” routing despite several close siblings.

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