Skip to main content
Glama

Microburbs Australian Property Data

State · Federal election results

states_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": {
      "state": "<state>"
    },
    "name": "states_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.
stateYesState or territory abbreviation: nsw, vic, qld, sa, wa, tas, act or nt.
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.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add operational context — and it does: coverage threshold (suburbs with ≥100 formal votes), ~7,500 suburbs per election, currency cutoff 2025-05-03, a 5¢ per-call price, and a pointer to the dataset doc for method and field list. It adds no contradiction with annotations. It does not discuss row volume or whether a state query returns thousands of suburb rows at once.

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 payload, then coverage, currency, doc link and price — a sensible ordering with little waste. The price line and the coverage sentence are both earning their place for an agent deciding whether to call. Slightly dense package prose but not padded.

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 carries the return-value burden and does reasonably well by naming the metrics and the suburb/state/national scopes. The doc pointer plus method reference covers the rest. The gaps are the unresolved grain question (suburb rows vs state aggregates) and how `from`/`to` map to election years.

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 baseline is 3. The description adds context by enumerating the measures the `fields` values correspond to (swings, TPP, informal vote, electorate, turnout), but it says nothing about the optional `from`/`to` window — notably the schema offers generic period formats (quarter/month/day) for a dataset that only exists at three election dates, which is left unresolved.

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 states concretely what is returned: first-preference share by party, two-party-preferred Labor v Coalition, swings, informal vote, electorate, plus state and national totals with turnout, for the 2019/2022/2025 federal elections. A reader knows the resource and the measures. It stops short of distinguishing itself from the near-identically named siblings (australia_… and suburbs_… federal election results), and 'how each suburb voted' makes it briefly unclear whether rows are suburbs or state aggregates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative, despite three sibling tools covering the same dataset at national and suburb scope. The required `state` parameter implies a state-scoped query, but nothing tells the agent to prefer australia_… for national-only data or suburbs_… for a single suburb, nor when to omit this tool.

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