Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_server

Create a new Discord server and become its owner, optionally from a template code. Use it to start a server from scratch or reuse an existing template.

Instructions

Create a new server (you become the owner). Optionally from a template code.

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": {
      "name": "<name>"
    },
    "name": "create_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoIcon: local path, URL or data URI
nameYes
template_codeNoServer template code (discord.new/<code>)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds the ownership side effect, which is genuine behavioral value, but says nothing about creation rate limits, whether the call fails if a name collides, or what happens when a template code is invalid.

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 compact sentences, front-loaded with the primary action and its side effect. No filler, no redundancy with the title or schema.

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 mutation with annotations and no output schema, the description covers the essentials but leaves gaps: the required name field is undocumented and the return value (presumably the new server object) is never mentioned. Adequate, not complete.

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 67%, with icon and template_code self-documented, leaving only the required name field bare. The description reinforces that template_code is optional and frames it as a starting point, but adds no format or validation detail beyond the schema's own "discord.new/<code>" hint.

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?

"Create a new server" gives a specific verb and resource, and "(you become the owner)" clarifies the resulting state. It implicitly contrasts with join_server, though it never names the alternative, so the distinction is left to inference.

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: creating a new server versus joining an existing one, with an optional template path. There is no explicit when-to-use guidance, no prerequisites, and no named alternative for the join case.

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