nc-mcp-server

vote_poll

Idempotent

Submit or change your vote on a Talk poll by selecting option indices, replacing any earlier vote. Works only for open polls and returns updated vote counts.

Instructions

Vote on a poll in a Talk conversation.

Voting replaces any previous vote — calling this again with different option_ids changes your vote. You cannot vote on closed polls.

Args: token: The conversation token. poll_id: The poll ID. Use get_poll to see available polls. option_ids: List of option indices to vote for (0-based). For example, if options are ["Yes", "No", "Maybe"], use [0] to vote "Yes", or [0, 2] to vote "Yes" and "Maybe". The number of choices must not exceed the poll's max_votes (0 means unlimited).

Returns: JSON object with updated poll details including your votes (voted_self) and current vote counts (if visible).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`token`	Yes
`poll_id`	Yes
`option_ids`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Sep 21, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond annotations, the description explains the mutation semantics: voting replaces any previous vote and re-calling with different option_ids changes the vote. It also discloses the closed-poll restriction and the max_votes constraint, which annotations alone do not convey.

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?

The description is efficiently organized: purpose, behavioral caveats, parameter details, and return format. Every sentence contributes actionable information, and the most important facts (purpose and vote replacement) are front-loaded.

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?

All 3 required parameters are documented, behavioral constraints and return shape are covered, and an output schema exists for return values. There is no critical missing context for selecting or invoking this tool.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates: token is defined as the conversation token, poll_id is tied to get_poll, and option_ids gets 0-based indexing, a worked example, and a max_votes limit explanation. This is more than enough for an agent to form correct arguments.

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 opening line 'Vote on a poll in a Talk conversation' names a specific verb, resource, and scope. It is clearly distinguishable from sibling poll tools such as create_poll, close_poll, and get_poll without needing to open their schemas.

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?

It tells the agent when to use the tool (to vote), when not to ('You cannot vote on closed polls'), and points to the prerequisite alternative 'Use get_poll to see available polls.' The replacement-vote behavior also clarifies the effect of repeated calls.

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

Deploy Server