No user-submitted related servers found.
Scored across 177 tools
Most tools carry explicit disambiguation hints ('use X instead of Y'), which rescues an otherwise extremely crowded surface. However there are many genuinely near-neighbour clusters — get_guild_info / get_server_stats / get_guild_settings / get_guild_preview / get_guild_features, and read_messages / search_messages / search_guild_messages / fetch_pinned_messages, and send_message / send_embed / send_multiple_embeds / reply_message / send_webhook_message / publish_announcement — that an agent must read carefully to pick correctly. Boundaries are documented but not self-evident from names alone.
Uniform discord_ prefix plus snake_case resource_action throughout, including a coherent discord_architect_* sub-namespace. The only wobble is verb drift for reads (list_ vs get_ vs fetch_ vs read_ vs explain_ vs verify_) and a few nouns that encode sub-resources (send_dm vs send_message, edit_dm_embed vs edit_embed), but the pattern is highly readable and predictable.
177 tools for one server is an extreme mismatch: no agent can reliably select from this surface, and much of it is long-tail (stickers, per-server bot avatars, application icon, reaction-role menus, styled Unicode names). The domain is genuinely large, but this should be split into toolsets (channels, members, permissions, guild settings, automod, build/architect) rather than a single flat list.
Coverage is unusually thorough — CRUD for channels, messages, threads/forums, members, roles, invites, webhooks, scheduled events, AutoMod, emoji/sticker, guild settings, onboarding, plus diagnostics, structure backup/restore and a declarative build pipeline. Remaining gaps are interactions/message components, slash-command registration, and voice/stage moderation, plus explicitly documented platform limits (no guild creation, no message-history export).