Skip to main content
Glama
googlarz

Signal MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

terminate_poll

End a poll you created to stop voting and notify participants with final results. Provide the poll's timestamp and your phone number, plus recipient or group ID.

Instructions

Close (terminate) a poll you created, stopping any further votes. All participants are notified that the poll has ended and can see the final results. Get target_timestamp from the original poll message in get_conversation — a poll has no separate ID, it's identified by its message timestamp. Only the poll creator can terminate their own poll. Provide either recipient (DM poll) or group_id (group poll).

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.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that voting stops, participants are notified, final results become visible, and only the creator can terminate. It also explains the identification method. It does not mention whether the action is irreversible, but 'stopping any further votes' strongly implies finality, and the disclosure is substantial for a tool of this simplicity.

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?

The description is a three-sentence paragraph with a logical flow: action, effects, identification, restriction, and parameter selection. Every sentence earns its place, and the main action is front-loaded. It is slightly verbose but not wasteful.

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?

The description covers all essential context for calling this tool: how to identify the poll (timestamp from get_conversation), the required fields (target_author, target_timestamp), the optional but exclusive parameters (recipient/group_id), and the creator restriction. It does not mention return values, but there is no output schema, and the behavior is straightforward enough that nothing critical is missing.

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 each parameter is already described. The description adds meaningful context beyond the schema: it explains that target_timestamp comes from the original poll message (and why it's used as the identifier), and it clarifies the mutual exclusivity of recipient vs. group_id. This adds value over the raw schema descriptions.

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 action (terminate/close) and the resource (a poll you created), and distinguishes it from sibling tools like vote_poll and create_poll by specifying the termination behavior and creator restriction. It also adds the important identification detail (via timestamp, not a separate ID).

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

Usage Guidelines4/5

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

The description provides clear when-to-use guidance: it's for closing a poll you created, and it explains the parameter selection (either recipient for DM polls or group_id for group polls). It also states the creator-only restriction. However, it does not explicitly mention when not to use it (e.g., if you're not the creator) or name alternative tools, though that is implicitly clear from context.

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