Skip to main content
Glama

Microburbs Australian Property Data

Australia · Federal election results

australia_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

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_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the description focuses on facts annotations cannot carry: the 100-formal-vote suburb threshold, geographic coverage (7,500 suburbs, 8 states/territories, Australia), currency to 2025-05-03, a documentation pointer and a 5¢ per-call price. Missing only how large a response is when called without filters.

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 core answer, then coverage, currency and price on separate short lines. Every segment carries information; the only minor waste is restating the URL slug-like dataset path at the end.

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

Completeness3/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 does a reasonable job listing the returned measures and coverage, but for an unfiltered national dataset at 5¢ per call it says nothing about response size, pagination or default field set when `fields` is omitted. Adequate, but a notable gap for an agent planning a call.

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 `from`, `to` and the full `fields` enumeration are already documented in the schema. The description adds a little semantic framing by naming the metrics available (first-preference share, TPP, swings, informal vote, turnout), but it does not explain that the schema has no geography filter and therefore returns all ~7,500 suburbs.

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 resource and scope: first-preference and two-party-preferred results by suburb for the 2019, 2022 and 2025 federal elections, plus state and national totals. An agent knows exactly what data comes back, though the definition never distinguishes this national-level tool from the similarly named `suburbs_demographics_federal_election_results` and `states_demographics_federal_election_results` 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?

Usage is implied by the dataset description (retrieve federal election results across geographies), and 'Also state and national totals' hints that this tool supersedes the narrower geography variants. However there is no explicit when-to-use/when-not statement, no mention of alternatives, and no guidance on when the state- or suburb-specific siblings should be preferred.

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