Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

sync_guild_template

Applies a Discord server template to an existing guild, updating its structure to match the template.

Instructions

Sync Guild Template. [PUT /guilds/{guild_id}/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": {
      "guild_id": "<guild_id>",
      "template_code": "<template_code>"
    },
    "name": "sync_guild_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
template_codeYesServer template code (discord.new/xyz)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare that this is a non-read-only, open-world, non-destructive mutation. The description adds only the HTTP method/path and does not disclose what the sync changes, whether it overwrites existing template state, what permissions are needed, or how the audit-log reason is used.

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?

The definition is short and front-loaded, with the endpoint compactly appended. The first sentence largely repeats the tool name, but there is no bloated or confusing wording.

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

Completeness2/5

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

For a non-destructive but still mutating tool with no output schema, the description is too thin. It does not explain the effect of syncing a template, when the operation should be used, or how it differs from the other guild-template tools in the sibling set.

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%, so all three parameters are already documented in the input schema. The description's endpoint mapping reinforces guild_id and template_code as path parameters, but adds no meaning beyond that, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Sync') and resource ('Guild Template'), plus the HTTP endpoint, so it is not a pure tautology. However, it never explains what 'sync' actually does to the template or guild, and it gives no differentiation from sibling tools such as modify_guild_template or use_guild_template.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus create, delete, get, modify, or use guild template siblings. The endpoint implies a distinct operation, but the description does not state prerequisites or selection criteria.

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