discord-server-mcp

list_servers

Read-only

Lists every Discord server your configured bots can access, showing owner, members, bot admin status, and invite links so you can verify coverage and add bots elsewhere.

Instructions

List every Discord server the configured bots can work on (the servers they were invited to): owner, members, which bot and whether it is administrator there, plus the links to add each bot to another server.

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

Input Schema

Name	Required	Description	Default
`bot`	No	Use this bot (name or id) instead of choosing automatically

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

A3.8/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 safety is covered by structured data. The description adds real value by disclosing the shape of what comes back (owner, member counts, per-bot administrator flag, invite links), but says nothing about pagination, rate limits, or behavior when no bots are configured.

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?

One front-loaded sentence does all the work: scope first, return contents second. The parenthetical is earned because it disambiguates which servers count as available.

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?

For a read-only, single-optional-parameter tool with no output schema, the description usefully stands in for the missing return-value documentation by listing the fields returned. Only the per-bot selection behavior and result volume remain undocumented.

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 the single optional `bot` parameter is documented there as "use this bot instead of choosing automatically." The description ignores the parameter entirely and speaks only of "the configured bots" in aggregate, so it adds no meaning beyond the schema; 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?

Specific verb plus resource ("List every Discord server the configured bots can work on") with the discovery scope clarified in parentheses as servers the bots were invited to. It also enumerates what each entry contains (owner, members, bot/admin status, invite links), which distinguishes it from list_bots and get_server.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the discovery step before per-server operations, and the parenthetical scopes it to invited servers. However, it never says when to prefer get_server or list_members for detail, nor does it name any exclusion or prerequisite.

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