discord-mcp-server

create_poll

Create interactive polls with buttons in Discord channels. Set questions, multiple options, duration, and allow single or multiple choices.

Instructions

Crée un sondage interactif avec boutons

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": {
      "channelId": "<channelId>",
      "question": "<question>",
      "options": "<options>"
    },
    "name": "create_poll"
  }
}

Input Schema

Name	Required	Description
`channelId`	Yes	ID du canal
`question`	Yes	Question du sondage
`options`	Yes	Options de réponse
`duration`	No	Durée en minutes (optionnel)
`allowMultiple`	No	Autoriser plusieurs choix

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool creates a poll but doesn't mention what happens after creation (e.g., where the poll appears, how users interact, if it's ephemeral or persistent, or any rate limits). This leaves significant gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence in French that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with no wasted information.

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

Completeness2/5

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

Given the tool's complexity (a mutation with 5 parameters), no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, response format, or error handling, making it inadequate for safe and effective use by an AI agent.

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 all parameters (channelId, question, options, duration, allowMultiple). The description adds no additional meaning beyond the schema, such as explaining the format of options or how duration affects the poll, meeting the baseline for high coverage.

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 clearly states the verb 'Crée' (creates) and the resource 'sondage interactif avec boutons' (interactive poll with buttons), making the purpose specific. It distinguishes from siblings like 'create_interactive_quiz' by specifying 'poll' rather than 'quiz', though it doesn't explicitly contrast them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'create_interactive_quiz' or 'create_button'. The description lacks context about prerequisites, such as needing a valid channel ID or permissions, or when polls are appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server