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 server overview

get_server_overview
Read-only

Retrieve a structured snapshot of a Discord server—identity, member and role counts, boost status, channel outline by category, and invite/DM pause state—to start server management tasks.

Instructions

Structured snapshot of a server: identity, member counts, boost status, channel outline grouped by category, and role count. The natural first call when starting work on a server. The outline holds only channels the bot can see; hidden_from_bot says how many others exist when any do. A running pause on invites or DMs is reported too.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_server_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
guildNoGuild (server) name or ID. Omit to use the default guild.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.0.2

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is to add behavior beyond that. It does add genuinely useful scope details: the outline is filtered to bot-visible channels, hidden_from_bot reports the remainder, and running invite/DM pauses are surfaced. It does not describe result shape, size limits, or how costly the call is, so it is good but not rich behavioral disclosure.

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?

Four short sentences: contents first, then usage cue, then two scoping caveats. It is front-loaded and every sentence carries information. Slightly more could be trimmed, but there is no filler or restatement of the title.

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

Completeness4/5

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

There is no output schema, so the description must carry the return-value burden, and it does by enumerating the snapshot sections and the hidden_from_bot/pause fields. For a single-parameter read tool this is nearly complete; the only gap is any hint about output shape or ordering.

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 coverage is 100% and the single guild parameter is fully documented in the schema, including the omit-to-use-default behavior. The description never mentions the guild parameter or how server resolution works (name vs. ID), so it adds nothing beyond the schema. 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 gives a concrete verb (structured snapshot) plus the resource (a server) and enumerates exactly what the snapshot contains: identity, member counts, boost status, channel outline by category, role count. That is far more specific than the title. It stops short of contrasting with adjacent siblings such as get_server_preview or get_server_widget, so an agent must infer the difference from the content list alone.

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

Usage Guidelines4/5

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

"The natural first call when starting work on a server" gives a clear positive usage context that tells an agent when to reach for this tool. There is no explicit when-not guidance and no named alternative for cases where a lighter lookup (e.g. a preview) would suffice, which keeps it out of the top band.

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