Skip to main content
Glama
ElectionData MCP

ElectionData MCP

data_access

Read-only

Get direct Parquet links plus ready Python and R code to load full election datasets locally without row limits, enabling machine learning and custom analysis.

Instructions

Direct Parquet links and ready code (Python, R) to load full datasets on the user's own machine, with no row limit. Good for machine learning.

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": "data_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlNo
datasetsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description usefully adds that output is Parquet links plus code and that there is no row limit. It does not disclose how the sql parameter changes the result (custom extract? filtered export?) or whether the links are pre-signed/expiring, which is material for a download tool.

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?

Two short sentences, front-loaded with the deliverable (links + code) and the key constraint (no row limit). The closing 'Good for machine learning' is slightly loose but does add routing value, so little is wasted.

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

Completeness2/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 shape need not be explained, but for a two-parameter tool with zero schema descriptions the definition should clarify sql vs datasets and their optionality. That gap, plus no note on link lifetime or scope, leaves the call underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and both parameters (sql, datasets) are undocumented in the schema. The description mentions 'full datasets' but never explains what sql does, how it interacts with datasets, or what happens when both are omitted — the agent is left guessing on the two inputs that drive the call.

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 concrete outcome — direct Parquet links plus ready-to-run Python/R load code for full datasets — so an agent can tell this is a bulk-download/export tool rather than a query tool. It does not name or contrast any sibling (e.g., run_sql, search_datasets), leaving differentiation 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 Guidelines3/5

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

'Good for machine learning' and 'no row limit' imply the selection condition: use this when the user needs complete data locally rather than aggregated results. There is no explicit when-not guidance or pointer to an alternative for smaller/aggregate needs.

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