Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

create_guild_template

Creates a reusable template from a Discord server (guild) using its ID and a template name, with optional description and audit-log reason.

Instructions

Create Guild Template. [POST /guilds/{guild_id}/templates]

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

Input Schema

NameRequiredDescriptionDefault
nameYesName
reasonNoReason (shown in the audit log)
guild_idYesServer (guild) ID
descriptionNo

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 readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered externally. The description adds nothing beyond the endpoint path: it does not mention required permissions (e.g., MANAGE_GUILD), rate limits, that the 'reason' parameter surfaces in the audit log, or what the created template captures.

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, front-loaded fragments with no padding; the route annotation is a compact useful detail. It is terse almost to a fault, but nothing is wasted.

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 mutation tool with no output schema, the description omits the permission requirements, side effects of template creation, and any indication of the response. The annotations cover safety but not operational context an agent would need to invoke this correctly.

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 75% with four well-named parameters, so the schema largely documents itself. The description adds no meaning beyond the route path (which implies guild_id), so the baseline of 3 applies.

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 and resource ('Create Guild Template') and the bracketed REST route [POST /guilds/{guild_id}/templates] confirms the scope. However, it is essentially a restatement of the tool name and gives no distinguishing detail versus siblings 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 the other template tools (modify, use, sync, get, delete). No prerequisites or context are offered, leaving the agent to infer usage from the name alone.

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