Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

get_guild_template

Read-only

Retrieve a Discord server template by its template code to inspect its configuration before applying or referencing it.

Instructions

Look up a server template by code. [GET /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": "get_guild_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the raw endpoint path, which hints that the lookup is global (not guild-scoped) and that the code is a path parameter, but it says nothing about auth requirements, caching, or what a returned template looks like.

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?

One sentence, front-loaded with the verb and resource; nothing is padded. The bracketed endpoint restates the route rather than the purpose and is marginal value, but it does not harm 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 one-parameter read tool with annotations and a fully documented schema, the essentials are present. However, with no output schema, the description should say at least what a template object contains (name, description, serialized source guild) — an agent gets no sense of the return value.

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% and the single parameter already documents the expected format (discord.new/xyz). The description adds no syntax, validation, or case-sensitivity detail beyond 'by code', so the schema carries the full load — baseline 3.

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?

States a specific verb ('look up') and resource ('server template') plus the selector ('by code'). The read framing implicitly separates it from create/delete/modify/sync/use siblings, though no sibling is named explicitly.

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 infer this is the read tool for fetching a template given a code. There is no explicit when-to-use condition, no mention of alternatives such as use_guild_template (which applies a template) versus this lookup, and no prerequisites stated.

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