Skip to main content
Glama
Sign In
discord-server-mcp

discord-server-mcp

by pr5ias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

add_bot

Register a Discord bot without sending its token through chat: use a private input box or a one-time local browser page to paste, verify, and save the token for immediate use.

Instructions

Add a Discord bot (several are supported) without the token ever going through the chat. method "box" (default) asks the app to show a private input box; if the app cannot, or the box is closed, it opens a one-time page on this computer (a http://127.0.0.1 link) where the user pastes the token in their browser. The token is checked and saved, and the bot can be used at once. Call it after the user created the bot (setup_check has the steps).

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

Input Schema

NameRequiredDescriptionDefault
labelNoName to remember the bot by; default: the bot's username
methodNobrowser = skip the box and give the page link straight awaybox
dry_runNoShow the requests that would be made without changing anything

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only supply readOnlyHint=false, so the description carries most of the burden and does so well: it discloses the fallback chain (box -> local http://127.0.0.1 page), that the page is one-time, and that the token is validated and saved with immediate usability. It omits failure behavior (invalid token, duplicate bot) and whether the write is reversible.

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?

Front-loaded with the action and the key safety guarantee, then the mechanics. The second sentence is long and clause-heavy but every clause adds operational information; nothing is filler.

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 zero-required-param, no-output-schema tool, this covers the important ground: prerequisite, method selection, fallback, and post-call state ('bot can be used at once'). What it lacks is what the agent gets back (label/id) and what happens on token rejection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning for 'method': box is the default, browser skips the box and returns the link immediately, and box degrades to browser when the app cannot show a box. dry_run and label are left to the schema.

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 ('Add a Discord bot') with the distinguishing scope note '(several are supported)', which separates it from list_bots, remove_bot and use_bot. The security property (token never goes through the chat) further pins down what this tool is for.

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?

Gives explicit ordering guidance: 'Call it after the user created the bot (setup_check has the steps)', routing the agent to the correct prerequisite tool. It also explains the two method modes, but never states when NOT to use it (e.g. if a bot already exists, check list_bots first).

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