Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

use_guild_template

Creates a new Discord server from a template code so you can launch a configured server and set its name, icon, and audit-log reason.

Instructions

Create a new server from a template. [POST /guilds/templates/{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": {
      "template_code": "<template_code>",
      "name": "<name>"
    },
    "name": "use_guild_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconNoIcon image: local file path, http(s) URL or data: URI
nameYesName
reasonNoReason (shown in the audit log)
template_codeYesServer template code (discord.new/xyz)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare a non-read-only, open-world, non-destructive mutation, so the safety profile is covered. The description adds only the raw endpoint path and nothing about required permissions, the heavy rate limiting on guild creation, or what side effects occur (e.g. channels/roles being copied from the template).

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 the action front-loaded and no filler. The bracketed endpoint is somewhat redundant with the tool's routing metadata but is compact and does not obstruct readability.

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 create-mutation with no output schema, the definition covers the essentials but leaves out the meaningful operational context: permission requirements, rate-limit behavior, and whether the response returns the new guild object. Annotations carry the safety profile, so this is adequate but thin.

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%, so all four parameters (icon, name, reason, template_code) are already documented in structured form. The description mentions template_code only as a path placeholder and adds no formatting guidance or constraints beyond the schema.

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 from a template" gives a clear verb (create), object (server/guild) and source (a template), which implicitly separates it from create_guild_template. It stops short of naming any sibling explicitly, so an agent must infer the distinction from the preposition alone.

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 only implied: an agent can reason that this applies when a template code already exists. There is no explicit when/when-not, no mention of the prerequisite that template_code must come from an existing template, and no routing to alternatives such as create_guild_template.

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