Skip to main content
Glama
googlarz

Signal MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

terminate_poll

Destructive

Close a poll you created to stop votes and display final results. Irreversible; only the creator can terminate.

Instructions

Close a poll you created so no more votes are accepted; participants see it as ended with final results. Irreversible. Use vote_poll to vote, create_poll to start a new one. Only the creator can terminate. target_author: your own E.164 number (accepted for symmetry with vote_poll; only the timestamp is sent); target_timestamp: ms timestamp of the poll (from create_poll or get_conversation). Give recipient (E.164) for a DM poll or group_id for a group poll; neither is an error. Contacts Signal's servers. Returns {status: 'poll terminated'}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNoGroup ID for a group poll — provide this OR recipient
recipientNoPhone number for a DM poll — provide this OR group_id
target_authorYesPhone number of the poll creator — must be your own number
target_timestampYesTimestamp of the poll message (from get_conversation)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.36.0
    • removedInput schema / properties / poll_id
      Removed value: -{
-  "description": "Poll ID from the original poll message data",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "target_author",
-  "target_timestamp",
-  "poll_id"
-]New value: +[
+  "target_author",
+  "target_timestamp"
+]
  2. 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 / poll_id / description
      Previous value: -"Poll ID from the original poll message"New value: +"Poll ID from the original poll message data"
    • 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"
    • changedInput schema / properties / target_author / description
      Previous value: -"Phone number of the poll creator (your own number)"New value: +"Phone number of the poll creator — must be your own number"
    • changedInput schema / properties / target_timestamp / description
      Previous value: -"Timestamp of the poll message"New value: +"Timestamp of the poll message (from get_conversation)"
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds real context beyond that: the action is irreversible, participants see final results, only the creator may act, and the call contacts Signal's servers. Strong additive disclosure, though the remote side-effect story could be marginally richer.

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 action and its irreversibility, then routing, then parameter notes, then the return value. Slightly dense but every sentence carries information an agent needs; no filler sentences.

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?

With no output schema, the description supplies the return shape ({status: 'poll terminated'}), the permission constraint, and the DM-vs-group addressing rule. For a destructive 4-parameter tool this covers everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining the odd target_author semantics ('accepted for symmetry with vote_poll; only the timestamp is sent'), the source of target_timestamp (create_poll or get_conversation), and that supplying neither recipient nor group_id is not an error.

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 (terminate) and resource (poll) with the scope of the effect: closing a poll you created so no more votes are accepted. It explicitly distinguishes itself from the two closest siblings, vote_poll and create_poll, so an agent can route correctly without reading either schema.

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 alternates with conditions ('Use vote_poll to vote, create_poll to start a new one') and a hard precondition ('Only the creator can terminate'). Nothing about when to choose this tool is 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