MCP Server for Discord community growth — find servers, analyze engagement, draft messages, auto-moderation. Free + Premium.
Server has 5 tools with basic schemas and descriptions, but significant quality gaps. All tools have input schemas with type definitions and descriptions present, meeting minimum requirements. However, descriptions are generic and lack LLM-optimized guidance on WHEN to use each tool or WHAT happens next. Parameter descriptions are minimal (e.g., 'Discord invite code' lacks format guidance). No output schemas documented, LLMs cannot predict response structure for chaining. Error handling is present but generic ('Error: {message}'). No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Tool names are reasonably clear (verb_noun pattern) but lack specificity, 'analyze_server_engagement' doesn't clarify what 'engagement' means or what metric is returned. No pagination support documented despite tools returning lists. Baseline: avg tool description 194 chars; these average ~120 chars and lack context. Avg params per tool: 4 (matches baseline), but descriptions average ~40 chars vs. 72 char baseline.
FREE: Analyze a Discord server's engagement (requires Bot token). Returns estimated activity level.
FREE: Draft a message for a Discord community. Uses AI to match community tone.
PREMIUM: Find the most relevant channels in a server for your project. Requires DEESEEK_API_KEY.
PREMIUM: Generate community moderation rules based on your community type. Requires DEESEEK_API_KEY.
FREE: Search for public Discord servers by keyword. Returns server names, member counts, descriptions.
No output schemas documented. LLMs cannot predict response structure, breaking tool chaining and forcing agents to parse unstructured text responses.
Descriptions lack LLM-optimized guidance. Missing WHEN to use each tool, WHAT it returns, and HOW to use results downstream. E.g., 'analyze_server_engagement' doesn't explain what 'engagement' metric is returned or how to interpret it.
Parameter descriptions are minimal and lack format/constraint guidance. E.g., 'server_invite' description doesn't specify accepted formats (discord.gg/XXX vs discord.com/invite/XXX vs bare code). LLMs will guess and fail.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | <=2025-11-25 | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot determine which tools are safe to retry or have side effects. All tools marked READ_ONLY in metadata but not in schema.
Error handling is generic. Responses return 'Error: {message}' with no recovery guidance. E.g., when invite is invalid, should suggest 'Try search_public_servers() first' or 'Check the invite format'.