discord-mcp-server

create_interactive_quiz

Create interactive quizzes in Discord channels with automatic answer validation, scoring, and visual feedback to engage community members.

Instructions

Créer un quiz interactif avec validation automatique et animations

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>",
      "correctIndex": "<correctIndex>"
    },
    "name": "create_interactive_quiz"
  }
}

Input Schema

Name	Required	Description	Default
`channelId`	Yes	ID du canal
`question`	Yes	Question du quiz
`options`	Yes	Options de réponse (2-4)
`correctIndex`	Yes	Index de la bonne réponse (0-3)
`points`	No	Points à gagner
`badge`	No	Badge à obtenir
`timeLimit`	No	Limite de temps en secondes
`difficulty`	No	Difficulté	medium
`category`	No	Catégorie du quiz
`theme`	No	Thème	gaming
`animationStyle`	No	Animation de réussite	confetti

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 provided, the description carries the full burden of behavioral disclosure. It mentions 'validation automatique et animations' but lacks details on permissions, side effects (e.g., if it posts to a channel), rate limits, or error handling. For a tool with 11 parameters and no annotations, this is insufficient.

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 that front-loads the core purpose without unnecessary words. Every part of the sentence contributes to understanding the tool's function, making it highly concise and well-structured.

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 complexity (11 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values, error cases, or behavioral nuances needed for effective use, leaving significant gaps in context.

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?

The schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description adds no additional parameter details beyond what's in the schema, so it meets the baseline of 3 without compensating or adding value.

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 action ('Créer un quiz interactif') and key features ('validation automatique et animations'), providing a specific verb and resource. However, it doesn't differentiate from sibling tools like 'create_poll' or 'create_button', which might have overlapping interactive functionality, so it doesn't reach the highest score.

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?

The description offers no guidance on when to use this tool versus alternatives, such as 'create_poll' or other interactive tools in the sibling list. There's no mention of prerequisites, context, or exclusions, leaving the agent with minimal usage direction.

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

Deploy Server