Skip to main content
Glama

Election Index

by org.electionindex
OverviewDiscussionsAdmin

Next election in a country

next_election
Read-only

The next elections in one country, however far ahead: polling day and whether it is declared, still tentative, or only expected within a period, what is elected, the counting authority, and when results are expected. Answers "When is the next election in Austria?" or "When are the US midterms?". National elections by default; level "regional" answers "When are the next state elections in Germany?". Covers 411 elections in 100 countries, 2021–2030, including 23 of the 27 EU member states, the 2026 US midterms in all 50 states and the certified 2024 US presidential result, with vote counts, in all 50 states and DC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoHow many upcoming elections to return, soonest first; default 3
levelNonational: the country votes; regional: a state, region or autonomous community elects its own parliament or head (German Länder, Spanish autonomous communities, Italian regions). Default national; the answer also counts upcoming regional elections
countryYesCountry name or ISO 3166-1 alpha-2 code, e.g. "Austria" or "AT", "United States" or "US"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaYesWhat this answer was built from; cite dataset_version
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / result / properties / elections / items / properties / races / items / properties / sources / items / properties / figures_in_html
      Added value: +{
+  "description": "For a results page: whether its own HTML shows a count (false: figures load by script or the page only links on; null: not read)",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedOutput schema / properties / result / properties / elections / items / properties / races / items / properties / sources / items / properties / oracle_reads
      Added value: +{
+  "description": "Settlement-oracle lab reads of this URL: right, wrong, unread, lab, at",
+  "type": [
+    "object",
+    "null"
+  ]
+}
  2. Changed3 schema fields changed
    • changedOutput schema / properties / result / properties / elections / items / properties / date / description
      Previous value: -"Polling day (YYYY-MM-DD)"New value: +"Polling day (YYYY-MM-DD); for an expected date, the last day of date_window"
    • changedOutput schema / properties / result / properties / elections / items / properties / date_status / description
      Previous value: -"declared, scheduled or tentative"New value: +"declared, tentative, or expected (no day set yet: see date_window)"
    • addedOutput schema / properties / result / properties / elections / items / properties / date_window
      Added value: +{
+  "description": "Only for date_status \"expected\": the period polling day is expected in",
+  "properties": {
+    "from": {
+      "description": "First possible day (YYYY-MM-DD)",
+      "type": "string"
+    },
+    "label": {
+      "description": "How we name the period, e.g. \"Q2 2029\"",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "to": {
+      "description": "Last possible day (YYYY-MM-DD)",
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}
  3. Changed4 schema fields changed
    • addedOutput schema / properties / result / properties / elections / items / properties / races / items / properties / results / items / properties / electorate
      Added value: +{
+  "description": "Registered voters",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
    • addedOutput schema / properties / result / properties / elections / items / properties / races / items / properties / results / items / properties / rows / items / properties / colour
      Added value: +{
+  "description": "Party colour (#RRGGBB, from Wikidata)",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / result / properties / elections / items / properties / races / items / properties / results / items / properties / rows / items / properties / party_id
      Added value: +{
+  "description": "Wikidata QID of the party",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / result / properties / elections / items / properties / races / items / properties / results / items / properties / turnout
      Added value: +{
+  "description": "Percent of registered voters who cast a ballot",
+  "type": [
+    "number",
+    "null"
+  ]
+}
  4. Changed7 schema fields changed
    • addedInput schema / properties / level
      Added value: +{
+  "description": "national: the country votes; regional: a state, region or autonomous community elects its own parliament or head (German Länder, Spanish autonomous communities, Italian regions). Default national; the answer also counts upcoming regional elections",
+  "enum": [
+    "national",
+    "regional",
+    "all"
+  ],
+  "type": "string"
+}
    • addedOutput schema / properties / result / properties / elections / items / properties / level
      Added value: +{
+  "description": "national or regional",
+  "type": "string"
+}
    • addedOutput schema / properties / result / properties / elections / items / properties / subdivision
      Added value: +{
+  "description": "ISO 3166-2 code of the state or region, if the election belongs to one",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / result / properties / elections / items / properties / subdivision_name
      Added value: +{
+  "description": "Name of that state or region",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / result / properties / level
      Added value: +{
+  "description": "national, regional or all",
+  "type": "string"
+}
    • addedOutput schema / properties / result / properties / regional_upcoming
      Added value: +{
+  "description": "Upcoming regional elections in this country (with level national); ask again with level \"regional\"",
+  "type": "integer"
+}
    • changedOutput schema / properties / result / properties / total_upcoming / description
      Previous value: -"All upcoming elections we list for this country"New value: +"All upcoming elections we list for this country at this level"
  5. Changed1 schema field changed
    • addedOutput schema / properties / result / properties / elections / items / properties / races / items / properties / results
      Added value: +{
+  "description": "Published counts we hold, oldest first (empty until a count is recorded)",
+  "items": {
+    "properties": {
+      "licence": {
+        "description": "Licence of the numbers",
+        "type": "string"
+      },
+      "published_at": {
+        "description": "When the publisher released it",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "publisher": {
+        "description": "Who published the count",
+        "type": "string"
+      },
+      "rows": {
+        "items": {
+          "properties": {
+            "candidate": {
+              "description": "Candidate or list",
+              "type": "string"
+            },
+            "party": {
+              "description": "Party, where recorded",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "seats": {
+              "description": "Seats or electoral votes won",
+              "type": [
+                "integer",
+                "null"
+              ]
+            },
+            "share": {
+              "description": "Percent of total votes",
+              "type": [
+                "number",
+                "null"
+              ]
+            },
+            "votes": {
+              "description": "Votes",
+              "type": "integer"
+            },
+            "winner": {
+              "description": "Most votes in this count",
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "source": {
+        "description": "File or page the numbers were copied from",
+        "type": "string"
+      },
+      "stage": {
+        "description": "Count stage of this version, e.g. final-result",
+        "type": "string"
+      },
+      "total_votes": {
+        "description": "Total votes cast in the race",
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
  6. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: the coverage envelope (411 elections, 100 countries, 2021–2030) tells the agent when results may be empty, and the declared/tentative/expected distinction discloses data-reliability nuance. It still says nothing about rate limits or freshness guarantees beyond the 2024 US result.

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

Conciseness3/5

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

The purpose is front-loaded and each early sentence carries information. The final coverage sentence, however, is bloated and partly redundant, re-listing US coverage ('2026 US midterms in all 50 states', 'certified 2024 US presidential result ... in all 50 states and DC') in a way that serves marketing more than tool selection.

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?

An output schema exists, so return-value documentation is not required, yet the description still characterizes the payload (polling day, status, counting authority, expected results). Combined with the stated country/date coverage, an agent has enough to call it correctly; only the relationship to sibling tools like upcoming_elections or when_final is left implicit.

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 all three parameters are already documented, including the level enum values and the count default. The description largely restates the level default and the national/regional distinction rather than adding syntax or format detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific resource and scope ('the next elections in one country, however far ahead') and enumerates exactly what is returned: polling day, declaration status, what is elected, counting authority, and expected results. The 'in one country' framing plus the national/regional distinction makes it separable from the plural sibling upcoming_elections without opening a schema.

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

Usage Guidelines4/5

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

Concrete question exemplars ('When is the next election in Austria?', 'When are the US midterms?') and an explicit rule that level='regional' is for 'When are the next state elections in Germany?' give clear context for when the tool applies. It never names an alternative tool or states when not to use it, so it stops short of full routing guidance.

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

All Election Index toolsInspect
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