vote.direct

Is a draft ready to publish

get_election_readiness

Read-onlyIdempotent

Whether a DRAFT election in the connected account can publish now: the checks the publish button runs (schedule, ballot, voter list, state rules, size), each blocker in the words publish would refuse with, warnings a board should hear (voting closes inside the state's notice period, no quorum on an HOA or condo, voters the emailed ballot cannot reach), the exact price and who pays it. Fixing one blocker can show the next, so ask again after each fix. Changes nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "election": "<election>"
    },
    "name": "get_election_readiness"
  }
}

Input Schema

Name	Required	Description	Default
`election`	Yes	The election's id or slug, from list_elections or create_election_draft.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and 'Changes nothing' reinforces rather than contradicts them. The description goes well beyond the annotations by enumerating what comes back (blockers phrased as publish would refuse, board-level warnings like notice-period and quorum issues, exact price and payer) and by disclosing the iterative reveal behavior.

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?

The purpose is front-loaded and every clause carries information — checks, blockers, warnings, price, retry behavior, non-mutation. It is delivered as one dense run-on sentence, which is heavier than needed but not padded.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-value burden, and it does: it names the categories of results (blockers, warnings, price) and their semantics. Nothing an agent needs to call or interpret this tool is missing.

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?

With one parameter at 100% schema coverage, the schema already documents that 'election' is an id or slug sourced from list_elections or create_election_draft. The description adds no further parameter meaning, 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?

States a specific verb and resource — whether a DRAFT election can publish now — and frames it as 'the checks the publish button runs', which distinguishes it cleanly from publish_election (does the publishing) and get_election (returns the election). An agent can route without opening any 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?

Clearly situates usage as a pre-publish check and adds the iterative rule 'Fixing one blocker can show the next, so ask again after each fix.' It does not explicitly name publish_election as the follow-up action or state when not to call it, so it falls short of full when/when-not/alternatives guidance.

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

All vote.direct 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?