Skip to main content
Glama
googlarz

Signal MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_poll

Create a poll with a question and options, then send it to a Signal contact or group so members can vote.

Instructions

Create a poll and send it to a contact or group. Use vote_poll to vote and terminate_poll to close it. question: the poll text; options: answer strings (at least 2, else an error); multi_select=true lets voters pick several answers (default false = single choice). Give recipient (E.164) for a DM or group_id (from list_groups) for a group; neither is an error. Contacts Signal's servers; not idempotent (each call sends a new poll); shares the 20-sends-per-minute rate limit; not saved to the local store. Returns {status: 'poll created', timestamp} — the timestamp (with your number as author) identifies the poll for vote_poll and terminate_poll.

Input Schema

NameRequiredDescriptionDefault
optionsYesList of answer options (minimum 2 required)
group_idNoGroup ID for a group poll — provide this OR recipient
questionYesThe poll question text
recipientNoPhone number for a DM poll — provide this OR group_id
multi_selectNoAllow voters to select multiple options (default: false = single choice only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • changedInput schema / properties / group_id / description
      Previous value: -"Group ID for a group poll"New value: +"Group ID for a group poll — provide this OR recipient"
    • changedInput schema / properties / multi_select / description
      Previous value: -"Allow multiple answer selection (default false)"New value: +"Allow voters to select multiple options (default: false = single choice only)"
    • changedInput schema / properties / options / description
      Previous value: -"List of answer options (at least 2)"New value: +"List of answer options (minimum 2 required)"
    • changedInput schema / properties / question / description
      Previous value: -"The poll question"New value: +"The poll question text"
    • changedInput schema / properties / recipient / description
      Previous value: -"Phone number for a DM poll"New value: +"Phone number for a DM poll — provide this OR group_id"
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it warns that each call contacts Signal's servers, is not idempotent, shares a 20-sends-per-minute rate limit, and is not saved to the local store. It also discloses the return shape {status, timestamp} and how the timestamp keys vote_poll/terminate_poll.

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?

Dense but front-loaded, leading with the action before branching into usage and parameter rules. Every clause carries information, though the packed single-paragraph form is slightly heavy.

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?

No output schema exists, but the description supplies the return shape and the identity key needed for follow-up calls. Combined with rich parameter and behavioral detail, an agent has everything needed to invoke it correctly.

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 100%, yet the description adds real meaning: options must have at least 2 or it errors, multi_select=true enables multi-answer (default single), recipient must be E.164, group_id comes from list_groups, and supplying neither is an error. This compensates for constraints the schema cannot express.

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+resource ('Create a poll') plus its delivery scope ('send it to a contact or group'). It explicitly names the sibling tools vote_poll and terminate_poll, so an agent can distinguish the lifecycle stages without opening 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?

Gives explicit routing ('Use vote_poll to vote and terminate_poll to close it') and states the selection rule for recipient (DM) vs group_id (group), including that providing neither is an error. Edge conditions are surfaced rather than left to inference.

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