Skip to main content
Glama

List federal vote days

list_vote_dates
Read-only

List available federal popular-vote days that have official result data, ordered newest first, so you can pick a date for vote analysis.

Instructions

List available federal popular-vote days with official result data (newest first).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior4/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 adds real value beyond them by disclosing the implicit filter (only days that have official result data) and the sort order (newest first). It does not say anything about how many days exist overall or whether the result set is complete, which keeps it from a 5.

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

Conciseness5/5

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

One sentence, front-loaded with the verb and resource, with the scoping condition and ordering packed into parentheticals. No filler words and nothing that could be cut without losing information.

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?

For a read-only, one-optional-parameter list tool with no output schema, the description covers what is returned, its ordering, and its inclusion criterion — enough to call it correctly. The remaining holes (pagination behavior, whether the list is exhaustive) are minor at this complexity level.

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?

The single 'limit' parameter has 0% schema description coverage, but its type, default of 15, and min/max bounds are expressed as JSON Schema constraints, so an agent can still call it correctly. The description does not mention paging or what 'newest first' combined with a limit means for truncation, leaving a modest gap.

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?

States a specific verb and resource ('List available federal popular-vote days') and narrows scope with two concrete qualifiers: only days with 'official result data' and ordering 'newest first'. An agent knows exactly what comes back, but the description never names or distinguishes any sibling tool, so it stops short of a 5.

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 statement, no prerequisite, and no named alternative. The phrase 'with official result data' hints that this is a discovery step before fetching results, but the agent must infer that workflow entirely on its own.

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

Deploy Server

Other Tools