Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

vote_in_poll

Cast or remove your vote in a Discord poll by specifying channel, message, and 1-based answer IDs; use an empty list to remove your vote.

Instructions

Vote in a poll: answer_ids are the 1-based answer numbers. An empty list removes your vote. [PUT /channels/{channel_id}/polls/{message_id}/answers/@me]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel_id": "<channel_id>",
      "message_id": "<message_id>",
      "answer_ids": "<answer_ids>"
    },
    "name": "vote_in_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
answer_idsYesAnswer IDs, e.g. ["1"] (empty removes your vote)
channel_idYesChannel ID (text, voice, thread, forum or DM channel)
message_idYesMessage ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds genuinely useful behavior beyond that: voting is idempotent-style upsert (empty list removes the vote) and the underlying PUT endpoint, which tells an agent this is a state-replacing operation on the caller's own vote.

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?

A single front-loaded sentence with the core semantics, plus a compact endpoint tag. Nothing is wasted, though the bracketed HTTP route is marginal value for an agent and could be trimmed.

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?

With three required, fully described parameters, no output schema, and annotations covering the safety profile, the description supplies everything needed to call the tool correctly, including the unvote semantics. Only the return behavior is unaddressed, which is acceptable given there is no output schema.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters are already documented, including the note that an empty answer_ids removes the vote. The description's '1-based answer numbers' framing adds slight clarity about the value domain but largely restates the schema, which is the expected baseline-3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Vote in a poll') and names the key parameter, so the operation is unambiguous. It does not explicitly contrast with siblings such as create_poll or end_poll, though their names make the distinction fairly self-evident.

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

Usage Guidelines3/5

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

The description notes that an empty answer_ids list removes your vote, which is effectively usage guidance for the unvote case. However, it gives no explicit when-to-use or when-not-to-use framing relative to alternatives like list_poll_answer_voters or end_poll; usage is implied rather than stated.

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