discord-server-mcp

set_server_bot

Select which configured bot handles a specific Discord server, or set it to auto to restore the default bot. Use dry_run to preview changes before applying.

Instructions

Choose which bot to use in a server that several configured bots are in (saved on this computer). "auto" goes back to the default bot.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>",
      "bot": "<bot>"
    },
    "name": "set_server_bot"
  }
}

Input Schema

Name	Required	Description
`bot`	Yes	Bot name or id, or "auto"
`server`	Yes	Server name or id
`dry_run`	No	Show the requests that would be made without changing anything

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 12, 2026

TDQS

B3.4/5.0

Behavior3/5

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

readOnlyHint=false already signals a mutation; the description adds that the choice is persisted locally ("saved on this computer"), which is real context. It does not say whether an authorization or bot-presence requirement applies, nor how existing settings are affected, and the dry_run safety valve is left entirely to the schema.

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?

Two short sentences with no filler, and the primary purpose is front-loaded ahead of the "auto" note. The middle clause ("that several configured bots are in") is slightly clumsy but still conveys a needed precondition.

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

Completeness3/5

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

For a three-parameter local-configuration mutation with no output schema and only a readOnly hint, the description covers the core behavior and the special "auto" value. It omits error/precondition behavior (what happens if the named bot is not present in that server) and confirmation of the return shape, leaving modest gaps.

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 dry_run is documented there, so the schema does the heavy lifting. The description contributes one genuinely new fact: that "auto" resolves to the default bot rather than being just another id value. Baseline 3 is appropriate.

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?

States a concrete verb and resource (choose which bot is used in a given server) and adds the scope condition that several configured bots must already exist. It does not explicitly distinguish itself from nearby siblings such as add_bot or use_bot, so the differentiation is only partial.

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?

The description implies the situation in which to use it (a server with multiple configured bots, selection saved on this computer) and explains that "auto" restores the default. It never states when not to use it or which sibling to pick instead, so guidance is implied rather than explicit.

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