discord-server-mcp

get_server

Read-only

Retrieves a Discord server overview—settings, categories, channels, roles, and bot permissions—so you can inspect the structure before making changes.

Instructions

Overview of a server: settings, every category with its channels (type, topic, forum tags), roles (top to bottom) and the bot's own permissions. Start here before changing anything.

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"
  }
}

Input Schema

Name	Required	Description	Default
`bot`	No	Use this bot (name or id) instead of choosing automatically
`server`	No	Server name or id. Optional when the bot is in one server or DISCORD_GUILD_ID is set.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful payload detail, including that roles are ordered top to bottom and that channels carry type, topic and forum tags. It says nothing about response size, pagination or behavior on very large servers, which matters for a tool that returns an entire server structure.

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?

Two sentences, front-loaded with the resource and its contents, followed by actionable guidance. Every phrase maps to something the agent needs and nothing is repeated.

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?

No output schema exists, so the description must describe the return shape and does so in reasonable detail. For a read-only two-parameter tool this is nearly complete; only expectations about result size or very large servers are left unstated.

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%, and both optional parameters are documented in-schema, including the DISCORD_GUILD_ID fallback. The description adds no meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and enumerates exactly what the overview contains: settings, categories with channels (type, topic, forum tags), roles in top-to-bottom order, and the bot's permissions. This distinguishes it cleanly from narrower siblings like list_roles, get_member or list_servers without needing those names.

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?

'Start here before changing anything' gives an explicit sequencing rule that points the agent at this tool before mutations such as edit_server, create_channel or delete_role. It stops short of naming alternatives or stating when not to use it (e.g. when only one category is needed).

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