Election Index

Election status

election_status

Read-only

Full record of one election: races, polls-close times, every count stage window (exit poll, election night, intermediate count, final result, government) with confidence and citation, the authority, sources, recorded vote counts, and whether the record is stale.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`election`	Yes	Election id, e.g. "latvia-parliamentary-2026"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	Yes	What this answer was built from; cite dataset_version
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 17, 2026

added

Output schema / properties / result / 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"
+  ]
+}

added

Output schema / properties / result / 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"
+  ]
+}

Changed3 schema fields changedOct 3, 2026

changedOutput schema / properties / result / 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 / 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 / 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"
+  ]
+}

Changed4 schema fields changedSep 30, 2026
- addedOutput schema / properties / result / properties / races / items / properties / results / items / properties / electorate
```
Added value: +{
+  "description": "Registered voters",
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / result / 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 / 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 / races / items / properties / results / items / properties / turnout
```
Added value: +{
+  "description": "Percent of registered voters who cast a ballot",
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

Changed3 schema fields changedSep 29, 2026

addedOutput schema / properties / result / properties / level

Added value: +{
+  "description": "national or regional",
+  "type": "string"
+}

addedOutput schema / properties / result / 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 / subdivision_name

Added value: +{
+  "description": "Name of that state or region",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 29, 2026

addedOutput schema / properties / result / 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"
+}

First observedSep 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and world-scope are covered. The description adds genuine behavioral value by disclosing the count-stage model (exit poll through government) with confidence/citation and a staleness flag. It does not say what makes a record stale, whether stale data is refreshed, or what happens with an unknown election id.

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?

A single front-loaded sentence that leads with the core object ("Full record of one election") and then enumerates contents. It is list-heavy and slightly run-on, but every clause describes actual returned data rather than filler.

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?

An output schema exists, so the description need not re-explain return values — making its content enumeration partly redundant — while the input side is fully schema-documented. The real gap is selection context: nothing tells the agent how this differs from next_election, upcoming_elections, or when_final, which is the main thing left unaddressed.

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?

Only one parameter, and the schema documents it at 100% coverage including a format example ("latvia-parliamentary-2026"). The description adds no syntax, validity, or lookup guidance beyond the schema. Per the baseline for high schema coverage, 3 is appropriate.

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 a specific resource — the full record of one election — and enumerates the substantive content (races, count-stage windows, authority, sources, vote counts, staleness). An agent can tell this returns a single election's detail record. It does not, however, explicitly contrast itself with siblings like next_election, upcoming_elections, or when_final, so differentiation is left to inference.

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 when-to-use guidance and no named alternative. With siblings such as next_election, upcoming_elections, and when_final clearly overlapping in the election domain, the description never says when this single-election lookup is the right call instead of those, nor does it state prerequisites (e.g., needing a valid election id).

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

All Election Index tools Inspect

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

Need Help?