Skip to main content
Glama

vote_poll

Cast your vote on an active Signal poll in a DM or group conversation. Supports single and multi-select polls.

Instructions

Cast your vote on an active Signal poll in a DM or group conversation. Your vote is delivered via signal-cli and is visible to all participants in real time. Each participant can vote once; re-voting overwrites the previous selection. For single-choice polls, provide exactly one option index in votes. For multi-select polls, provide all chosen indices in a single call — partial updates are not supported. votes are 0-based indices corresponding to the options array from the original create_poll call. Get target_author, target_timestamp, and poll_id from the poll message returned by get_conversation. Provide exactly one of recipient (for a DM poll) or group_id (for a group poll). Voting on a terminated poll returns an error. Use terminate_poll to close a poll you created and freeze the results. Use when responding to an open poll in a conversation. Do NOT use to create a poll — use create_poll instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
target_authorYesPhone number of the poll creator (E.164)
target_timestampYesTimestamp of the poll message (from get_conversation)
poll_idYesPoll ID from the poll message data
votesYesOption indices to vote for (0-based). Single item for single-choice polls.
recipientNoPhone number for a DM poll — provide this OR group_id
group_idNoGroup ID for a group poll — provide this OR recipient
Behavior5/5

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

Discloses that votes are visible in real time, voting on terminated polls returns error, re-voting overwrites previous selection, and partial updates are not supported for multi-select polls. No annotations provided, so description fully covers behavioral traits.

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?

Description is informative but somewhat lengthy (4 sentences). It front-loads purpose and then details behavior and parameter usage. Slightly verbose but well-organized.

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?

Covers parameter derivation (from get_conversation), error conditions (terminated poll), and usage distinctions between single/multi-choice polls. No output schema, so return values not needed. Complete for a voting tool.

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

Parameters4/5

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

Input schema has 100% coverage with descriptions, but the description adds context: explains 0-based indexing for votes, relationship to create_poll options, and mutual exclusivity of recipient vs group_id. Value added beyond schema.

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 clearly states the tool casts votes on active Signal polls in DMs or groups, distinguishing it from sibling tools like create_poll and terminate_poll.

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?

Explicitly says when to use (responding to open poll), when not to (creating polls), and references alternatives (create_poll, terminate_poll). Also explains single vote per participant, re-voting overwrites, and how to obtain required parameters from get_conversation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server