Skip to main content
Glama

Election Index

by org.electionindex
OverviewDiscussionsAdmin

Upcoming elections

upcoming_elections
Read-only

List elections by date range and/or country, soonest first, with each race's expected count stage right now. Answers "Which elections are in Europe this autumn?", "Which elections are this month?" or "What elections does Germany have coming up?". Without dates it starts today; with a country and no end date it covers every future election of that country, otherwise the next 365 days. 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
toNoEnd date YYYY-MM-DD; default +365 days, or no end when a country is given
fromNoStart date YYYY-MM-DD; default today
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 all
limitNoMost elections to return, soonest first; default 25, max 200. Narrow with from/to or country for more.
countryNoCountry name or ISO 3166-1 alpha-2 code, e.g. "Austria" or "AT", "United States" or "US"
include_discoveredNoAlso list elections found on Wikidata but not yet verified by Global Election Index

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. Changed1 schema field changed
    • changedInput schema / properties / include_discovered / description
      Previous value: -"Also list elections found on Wikidata but not yet verified by Election Index"New value: +"Also list elections found on Wikidata but not yet verified by Global Election Index"
  4. 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"
+  ]
+}
  5. Changed4 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 all",
+  "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"
+  ]
+}
  6. 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"
+}
  7. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2, e.g. \"LV\""New value: +"Country name or ISO 3166-1 alpha-2 code, e.g. \"Austria\" or \"AT\", \"United States\" or \"US\""
    • changedInput schema / properties / from / description
      Previous value: -"YYYY-MM-DD"New value: +"Start date YYYY-MM-DD; default today"
    • changedInput schema / properties / to / description
      Previous value: -"YYYY-MM-DD"New value: +"End date YYYY-MM-DD; default +365 days, or no end when a country is given"
  8. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Most elections to return, soonest first; default 25, max 200. Narrow with from/to or country for more.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedOutput schema / properties / result / properties / returned
      Added value: +{
+  "description": "Elections in this answer (see limit)",
+  "type": "integer"
+}
    • addedOutput schema / properties / result / properties / total
      Added value: +{
+  "description": "Elections matching the filters",
+  "type": "integer"
+}
  9. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral context: the default date-window logic that silently changes results, and dataset scope (411 elections, 2021–2030). It stops short of stating return shape or pagination, but that is acceptable given an output schema exists.

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 purpose, sort order, and defaults before the example questions. The final coverage paragraph (EU members, US midterms, vote counts in 50 states) is marketing-flavored and slightly padded, but still conveys scope.

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 an output schema present, return values need not be explained, and the description covers purpose, defaults, scope, and example intents. It is largely complete for a 6-param optional-argument list tool, missing only explicit sibling disambiguation.

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 coverage is 100% and each parameter already documents its default and format, so the description is not load-bearing here. It reinforces the default interactions between from/to/country but adds little syntax or semantics beyond the schema; baseline 3 is appropriate.

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?

States a specific verb and resource ('List elections') plus sort order ('soonest first') and an unusual added field (expected count stage). This distinguishes it from siblings like next_election (singular) and election_status.

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?

Gives concrete example questions and, more usefully, the default resolution rules (no dates = today; country-only = all future; otherwise 365 days), which tell the agent how calls behave. It does not explicitly route against siblings such as next_election or election_status, so it falls short of a 5.

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