Skip to main content
Glama

vote.direct

by direct.vote
OverviewDiscussionsAdmin

Start an election for someone without an account

start_election_draft

Build a complete election (ballot, schedule, verification, voter emails) for a person who does not have a vote.direct account yet, and get the link where they claim it: they open it, create an account with their email, and the election appears in their dashboard ready to review and publish. Nothing is charged and no voter is contacted until they do. The link expires in 48 hours. For a person who has an account, or will sign in, create_election_draft works in their account directly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoTwo-letter US state code of the association (e.g. CA). Turns on that state's election-law checks before publishing.
titleYesElection title voters see, e.g. "2026 Board of Directors Election".
quorumNoOptional quorum: {type: "percentage" | "count", threshold}. E.g. {type: "percentage", threshold: 25} means a quarter of eligible voters must vote.
votersNoThe eligible voters (the roster), one per owner/member. Email addresses only; people reached by text or mail are added by the organizer on the election page.
resultsNoafter_close (default): voters see results once voting closes. live: running totals while voting is open. owner_only: only the organizer sees results.
opens_atNoWhen voting opens, ISO 8601 with offset. Omit to open when published.
timezoneYesIANA timezone of the association, e.g. America/Denver. Voters see times in it.
closes_atYesWhen voting closes, ISO 8601 with offset, e.g. 2026-11-12T17:00:00-07:00. Must be in the future.
questionsYesThe ballot, in order.
vote_typeNoWhat the vote decides, for the state-law checks.
descriptionNoOptional instructions or background shown above the ballot. Plain text.
verificationNoemail: every voter confirms a code sent to their email (included free). email_or_sms: voters may also confirm by text message (paid elections only; elections of 25 voters or fewer are email-only).
secret_ballotNoKeep who voted for what private from the organizer. Defaults to true.
community_typeNohoa or condo, when the state rules differ between them.
organization_nameNoAssociation name shown to voters and used as the email sender name. Defaults to the account's organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false, so the safety profile is partly covered, but the description adds substantial behavior beyond them: nothing is charged and no voter is contacted until the recipient acts, and the claim link expires in 48 hours. It stops short of describing what happens to a draft that is never claimed or any auth/rate considerations, so it is not 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.

Conciseness4/5

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

Front-loaded with the core action and the claim-link behavior, then the cost/contact guarantee, expiry, and the sibling alternative. It is on the longer side for a description, but each sentence carries a distinct fact, so almost nothing is wasted.

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 complex 15-parameter creation tool with no output schema, the description covers the outcome (a claim link that materializes the election in the recipient's dashboard ready to review and publish), the safety-relevant guarantees, and the sibling alternative. It does not explain what the tool returns at call time versus at claim time, a minor remaining gap.

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 description coverage is 100% with 15 rich nested parameters, including enums, quorum semantics, and voting-type rules, all documented in the schema itself. The description adds almost no parameter-level detail (it mentions ballot, schedule, verification, voter emails at a high level only), so 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?

The description states a specific action (build a complete election) on a specific resource (ballot, schedule, verification, voter emails) and names the exact mechanism: a claim link for a person without an account. It explicitly distinguishes itself from the sibling create_election_draft by naming it and stating the alternative condition (person already has or will create an account in their own account).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit routing: use this tool for a person without an account; use create_election_draft for a person who has an account or will sign in. The exclusion condition is stated plainly, so an agent can select between the two siblings without inference.

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

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