Skip to main content
Glama
Sign In
Discord MCP - Discord server management MCP for AI agents

Discord MCP - Discord server management MCP for AI agents

by OrygnsCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get poll results

get_poll_results
Read-only

Retrieve current tallies for a Discord poll message, optionally listing who voted for each answer. Use it to check live poll outcomes and voter breakdowns by channel and message ID.

Instructions

Current tallies for a poll message. With include_voters, also who voted for each answer.

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": "<channel>",
      "message_id": "<message_id>"
    },
    "name": "get_poll_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.
channelYesChannel name or ID.
message_idYesMessage ID, or the message's link.
include_votersNoAlso list the people who chose each answer.
voters_per_answerNoHow many voters to list per answer when include_voters is on. Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.4.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / include_voters
      Added value: +{
+  "description": "Also list the people who chose each answer.",
+  "type": "boolean"
+}
    • addedInput schema / properties / message_id / description
      Added value: +"Message ID, or the message's link."
    • addedInput schema / properties / voters_per_answer
      Added value: +{
+  "description": "How many voters to list per answer when include_voters is on. Default 100.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

B3.4/5.0
Behavior3/5

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

readOnlyHint=true already declares this is a safe read, so the description's burden is lower. It adds the useful behavioral detail that include_voters extends the response to voter identity per answer, but says nothing about permissions, rate limits, or how tallies behave for ended polls.

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?

Two short sentences, front-loaded with the core behavior and with no wasted wording. It is arguably too terse rather than too long, but structurally it is clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters, no output schema, and full schema coverage, the description covers the call mechanics adequately. However, since there is no output schema, the description should say more about the shape of the returned tallies (per-answer counts, voter list truncation) than the single word 'tallies' conveys.

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 description coverage is 100%, so the schema already documents guild, channel, message_id, include_voters, and voters_per_answer. The description restates the include_voters semantics without adding format or interaction detail (e.g., how voters_per_answer interacts with the output). Baseline 3 applies.

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?

The description names the specific resource (a poll message) and what is returned (current tallies), which is enough to distinguish it from siblings like create_poll and end_poll. It is a noun phrase rather than a verb phrase, but the intent is unambiguous.

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?

Usage is implied rather than stated: an agent can infer it should call this to read results of an existing poll. There is no explicit when-to-use versus alternatives (e.g., after end_poll, or versus get_reactions), and no stated prerequisites such as permissions or whether the poll must still be open.

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